Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0403cf906d6678940c1d704477df30ebe4f896958544b41cf78aa9cd842a7940

Tx prefix hash: 6983ecb252cfb5bc098b53c66db50e0efad1d6c76f42468b282e236084532f89
Tx public key: 8ff8e5aa43c3bea41196fa463073b25ac01ba3bccdec81ca1845f5d20e843c74
Timestamp: 1702618110 Timestamp [UCT]: 2023-12-15 05:28:30 Age [y:d:h:m:s]: 01:076:00:44:19
Block: 913442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315455 RingCT/type: yes/0
Extra: 018ff8e5aa43c3bea41196fa463073b25ac01ba3bccdec81ca1845f5d20e843c7402110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0648b6c6ea784d9a73437d5b0960ac2bc6e1afe1e18d9673d4e9b99518c937c 0.600000000000 1370710 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": 913452, "vin": [ { "gen": { "height": 913442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0648b6c6ea784d9a73437d5b0960ac2bc6e1afe1e18d9673d4e9b99518c937c" } } ], "extra": [ 1, 143, 248, 229, 170, 67, 195, 190, 164, 17, 150, 250, 70, 48, 115, 178, 90, 192, 27, 163, 188, 205, 236, 129, 202, 24, 69, 245, 210, 14, 132, 60, 116, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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