Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5af8b38022c3c3ccf134dda0c3204bcb545ae07b7e0080052ec1db46de5ff0a

Tx prefix hash: 71b61ac3120273f7d72c8b34cf9f0cf625a0888d8a3ceb04c9231a602ef256e9
Tx public key: ca970c12d40a4ed1349d0eb7f9e1f8b39cb2d684d2fa02b7ee28b8d0408de126
Timestamp: 1752600668 Timestamp [UTC]: 2025-07-15 17:31:08 Age [y:d:h:m:s]: 00:298:16:16:21
Block: 1326162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204841 RingCT/type: yes/0
Extra: 01ca970c12d40a4ed1349d0eb7f9e1f8b39cb2d684d2fa02b7ee28b8d0408de126021100000002a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 24c61fd5b70ddd9903cf2fc9d7e3f644408ceab45f281ae0b46abdd015936fec 0.000600000000 1813911 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": 1326172, "vin": [ { "gen": { "height": 1326162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24c61fd5b70ddd9903cf2fc9d7e3f644408ceab45f281ae0b46abdd015936fec" } } ], "extra": [ 1, 202, 151, 12, 18, 212, 10, 78, 209, 52, 157, 14, 183, 249, 225, 248, 179, 156, 178, 214, 132, 210, 250, 2, 183, 238, 40, 184, 208, 64, 141, 225, 38, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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: