Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e7ed9f4b4bc8e9b509c50bcbeb045c8a4fb9ce4df2d4b7d5ec865bb555d04af

Tx prefix hash: 3bc303f9a841105d75566c11f31f0f902a067c30ac3b2dc223c82ec665964baf
Tx public key: 72d2f6e9924382d3d0db65add001e3a1abef5747799413a7f3623e6bf46c1c39
Timestamp: 1721945764 Timestamp [UCT]: 2024-07-25 22:16:04 Age [y:d:h:m:s]: 00:256:13:03:18
Block: 1073683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183260 RingCT/type: yes/0
Extra: 0172d2f6e9924382d3d0db65add001e3a1abef5747799413a7f3623e6bf46c1c3902110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7fdd06a546929b95d1b46fd8e8d7e8c99247f1ff195f57e06890478f1cd24a8 0.600000000000 1546188 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": 1073693, "vin": [ { "gen": { "height": 1073683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7fdd06a546929b95d1b46fd8e8d7e8c99247f1ff195f57e06890478f1cd24a8" } } ], "extra": [ 1, 114, 210, 246, 233, 146, 67, 130, 211, 208, 219, 101, 173, 208, 1, 227, 161, 171, 239, 87, 71, 121, 148, 19, 167, 243, 98, 62, 107, 244, 108, 28, 57, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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