Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ea65b3064eabbdfff7393b07c0b2e2baded6391c62400aa72786effafd323291

Tx prefix hash: 7cd814b12183ffcc57ec8fe8a6caba1dade5b1107e38d4fe9464ae67cb5f752a
Tx public key: 0108470296d768f533d202f4f94a08da1406db0ba17b4a6007c85219f2b0525a
Timestamp: 1744095959 Timestamp [UTC]: 2025-04-08 07:05:59 Age [y:d:h:m:s]: 01:036:23:48:11
Block: 1256815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277373 RingCT/type: yes/0
Extra: 010108470296d768f533d202f4f94a08da1406db0ba17b4a6007c85219f2b0525a021100000004dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cbf13e96ff239b65999209e5f46c9178e30fd01c8809785aaf5c0989e7f6b229 0.000600000000 1743932 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1256825, "vin": [ { "gen": { "height": 1256815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbf13e96ff239b65999209e5f46c9178e30fd01c8809785aaf5c0989e7f6b229" } } ], "extra": [ 1, 1, 8, 71, 2, 150, 215, 104, 245, 51, 210, 2, 244, 249, 74, 8, 218, 20, 6, 219, 11, 161, 123, 74, 96, 7, 200, 82, 25, 242, 176, 82, 90, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: