Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c2bcb7b6e8a8221b139de3d5dae2554a38ee383482f734cd4b3ef08a6059d4b

Tx prefix hash: dccb78c66f5f06b59638cc88d846806b2f586e8e1eec979d1587fe5c76c1a44e
Tx public key: 352a11f156b4551fbccd2e80528741c33776985d35a368e97ef6c81628b94fa3
Timestamp: 1711322084 Timestamp [UCT]: 2024-03-24 23:14:44 Age [y:d:h:m:s]: 01:050:19:25:26
Block: 985630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297301 RingCT/type: yes/0
Extra: 01352a11f156b4551fbccd2e80528741c33776985d35a368e97ef6c81628b94fa30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b58d84c72219d8d54c79f53962de5db068c3b6c07cac4e6501bdcc3a1309f58 0.600000000000 1445847 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": 985640, "vin": [ { "gen": { "height": 985630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b58d84c72219d8d54c79f53962de5db068c3b6c07cac4e6501bdcc3a1309f58" } } ], "extra": [ 1, 53, 42, 17, 241, 86, 180, 85, 31, 188, 205, 46, 128, 82, 135, 65, 195, 55, 118, 152, 93, 53, 163, 104, 233, 126, 246, 200, 22, 40, 185, 79, 163, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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