Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99229e0d25de54cf23d72c232845755f3ef11af9ac0e4421abb0f8fc15a4872b

Tx prefix hash: 3ea051225d64943ec47ba6e15d78bba62feb05a017d1a964ee2b70bc721ab7a0
Tx public key: 3ac04adf22e594638ba53a58e10ba8aa191ab7dcb6a7a16d3d140c9ae2d17817
Timestamp: 1762234804 Timestamp [UCT]: 2025-11-04 05:40:04 Age [y:d:h:m:s]: 00:006:15:54:18
Block: 1404579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4772 RingCT/type: yes/0
Extra: 013ac04adf22e594638ba53a58e10ba8aa191ab7dcb6a7a16d3d140c9ae2d1781702110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae6dc86c9925b0c12c14891a20a638ac8a5c8f013453a58969cfcbca4cc09594 0.600000000000 1892938 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 dinasty-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": 1404589, "vin": [ { "gen": { "height": 1404579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae6dc86c9925b0c12c14891a20a638ac8a5c8f013453a58969cfcbca4cc09594" } } ], "extra": [ 1, 58, 192, 74, 223, 34, 229, 148, 99, 139, 165, 58, 88, 225, 11, 168, 170, 25, 26, 183, 220, 182, 167, 161, 109, 61, 20, 12, 154, 226, 209, 120, 23, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8