Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26fd14c27402fd245e6cecd305b36170a42eb32f987d17f6c117f340b1813ab3

Tx prefix hash: ef6140de38660a413b95abc1967f2c601d3ec8f6206d713b75e8179e63f52bc2
Tx public key: 8d97de68f05912b1d22ac9b7a14fae2b9932811af870553cac7cf3a35b2441f6
Timestamp: 1770334937 Timestamp [UTC]: 2026-02-05 23:42:17 Age [y:d:h:m:s]: 00:000:03:45:50
Block: 1471549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 112 RingCT/type: yes/0
Extra: 018d97de68f05912b1d22ac9b7a14fae2b9932811af870553cac7cf3a35b2441f60208016f0a0a3225e7df

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1029815081e42242d4494ae29ad767d25fcfa86c358694fbf1db92daba7348f3 0.000600000000 1960821 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": 1471559, "vin": [ { "gen": { "height": 1471549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1029815081e42242d4494ae29ad767d25fcfa86c358694fbf1db92daba7348f3" } } ], "extra": [ 1, 141, 151, 222, 104, 240, 89, 18, 177, 210, 42, 201, 183, 161, 79, 174, 43, 153, 50, 129, 26, 248, 112, 85, 60, 172, 124, 243, 163, 91, 36, 65, 246, 2, 8, 1, 111, 10, 10, 50, 37, 231, 223 ], "rct_signatures": { "type": 0 } }


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