Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6967b018d6406855801072959d5fdb654008cc2319ae7be281df74c6205371f1

Tx prefix hash: 3baadcce3889808d3902853e5b58d5051d86234252270e1718b24d57e8d3461b
Tx public key: 289a96a814eb7eab9c58d1443606e8bf8f991c3e14912d3b655391c0e5e0ca0f
Timestamp: 1751269888 Timestamp [UCT]: 2025-06-30 07:51:28 Age [y:d:h:m:s]: 00:140:15:11:40
Block: 1315697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98707 RingCT/type: yes/0
Extra: 01289a96a814eb7eab9c58d1443606e8bf8f991c3e14912d3b655391c0e5e0ca0f0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c519c1c7697293af5c703f7e2f89af11f3d96a7ae28f64a7c88ea64f84642526 0.600000000000 1803352 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": 1315707, "vin": [ { "gen": { "height": 1315697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c519c1c7697293af5c703f7e2f89af11f3d96a7ae28f64a7c88ea64f84642526" } } ], "extra": [ 1, 40, 154, 150, 168, 20, 235, 126, 171, 156, 88, 209, 68, 54, 6, 232, 191, 143, 153, 28, 62, 20, 145, 45, 59, 101, 83, 145, 192, 229, 224, 202, 15, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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