Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 983d9111dfd7c80d9931e45efa75f070cccd2a04bf138856e6cd30508d6e19c5

Tx prefix hash: 41d5b9a15b4c3d73ed334cc6fd0194382630783b95f45c1f42c41e75dc012cb7
Tx public key: ef6bca33e90bd12b3cddc57f1101f213e6ceb1e6d52b50ef44873be065f3083d
Timestamp: 1771124399 Timestamp [UTC]: 2026-02-15 02:59:59 Age [y:d:h:m:s]: 00:095:16:55:57
Block: 1478048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61895 RingCT/type: yes/0
Extra: 01ef6bca33e90bd12b3cddc57f1101f213e6ceb1e6d52b50ef44873be065f3083d021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d0d30022ec90b8edde9ae313e81a6cbf7e45fd880994fd2fa1880d9b1e8530d7 0.000600000000 1967370 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": 1478058, "vin": [ { "gen": { "height": 1478048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0d30022ec90b8edde9ae313e81a6cbf7e45fd880994fd2fa1880d9b1e8530d7" } } ], "extra": [ 1, 239, 107, 202, 51, 233, 11, 209, 43, 60, 221, 197, 127, 17, 1, 242, 19, 230, 206, 177, 230, 213, 43, 80, 239, 68, 135, 59, 224, 101, 243, 8, 61, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: