Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9ae97c1482bfeed314a72daff7eeb80460b36c82f66980f79ebbee65830039e

Tx prefix hash: 9c12a8ac65efa4f615f353c93f33948d0b45854152e5a74e9bad130e1e4c6834
Tx public key: 3999e10a75e028e60db9c2908eb631e6a1a692c3e617acf10ebc145fde0f0b25
Timestamp: 1727756476 Timestamp [UCT]: 2024-10-01 04:21:16 Age [y:d:h:m:s]: 00:261:18:26:20
Block: 1121863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186790 RingCT/type: yes/0
Extra: 013999e10a75e028e60db9c2908eb631e6a1a692c3e617acf10ebc145fde0f0b25021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54dea5520f1efc21a7a1ff5bfc41da035f9b9b540ee22c1580ad1f210397cd08 0.600000000000 1604220 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": 1121873, "vin": [ { "gen": { "height": 1121863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54dea5520f1efc21a7a1ff5bfc41da035f9b9b540ee22c1580ad1f210397cd08" } } ], "extra": [ 1, 57, 153, 225, 10, 117, 224, 40, 230, 13, 185, 194, 144, 142, 182, 49, 230, 161, 166, 146, 195, 230, 23, 172, 241, 14, 188, 20, 95, 222, 15, 11, 37, 2, 17, 0, 0, 0, 1, 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