Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0084d89e017e59b2127bf3dc8ead37f4159dcafb97360768e0b72de9e31a36b4

Tx prefix hash: e51ff6c942ad9aaca2f21b7f5e0d7f448beb0162c1896d43c5dcd67376bee3b1
Tx public key: 2e28f4940c0a3704219c0cd413ac869d546d231681e90cb54add752735c4a44b
Timestamp: 1745613548 Timestamp [UTC]: 2025-04-25 20:39:08 Age [y:d:h:m:s]: 01:209:12:24:14
Block: 1269391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413911 RingCT/type: yes/0
Extra: 012e28f4940c0a3704219c0cd413ac869d546d231681e90cb54add752735c4a44b021100000002e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2e519e19d237c0b9592cee7da385448909cf0dedede13b066f84f1281b10f1f 0.000600000000 1756626 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": 1269401, "vin": [ { "gen": { "height": 1269391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2e519e19d237c0b9592cee7da385448909cf0dedede13b066f84f1281b10f1f" } } ], "extra": [ 1, 46, 40, 244, 148, 12, 10, 55, 4, 33, 156, 12, 212, 19, 172, 134, 157, 84, 109, 35, 22, 129, 233, 12, 181, 74, 221, 117, 39, 53, 196, 164, 75, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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: