Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df20c0274c8b915feedd8a7cf009a7e74605402a0e319f154d866eac04eba163

Tx prefix hash: a830de580c8b6672a966ab0e84fd2b55431c03c313f577f5882f7758589dc2d3
Tx public key: b75815ba2bbdcb45031ed468c7bbb3cf884b2e6ad1e8ff84cf8509db1d4d26b4
Timestamp: 1772258848 Timestamp [UTC]: 2026-02-28 06:07:28 Age [y:d:h:m:s]: 00:266:04:38:10
Block: 1487434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195926 RingCT/type: yes/0
Extra: 01b75815ba2bbdcb45031ed468c7bbb3cf884b2e6ad1e8ff84cf8509db1d4d26b4021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 085132455779cf39fd6b3d55e64735c69ca40d0eccdf5e509f2f9fc53bd14a50 0.000600000000 1976904 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": 1487444, "vin": [ { "gen": { "height": 1487434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "085132455779cf39fd6b3d55e64735c69ca40d0eccdf5e509f2f9fc53bd14a50" } } ], "extra": [ 1, 183, 88, 21, 186, 43, 189, 203, 69, 3, 30, 212, 104, 199, 187, 179, 207, 136, 75, 46, 106, 209, 232, 255, 132, 207, 133, 9, 219, 29, 77, 38, 180, 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: