Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0e6a749ebf495631699f4a4c8837d6a8220929a4cc664f68d3c83acb6dd18ab

Tx prefix hash: 2b0f0eb35ed01c2e6d7967013648092c30c88d85cec917efb55a98b0fb14d5cf
Tx public key: b4fe952525b8630426b4c5928e8b8136c0914bf0737e5925dc7167fdc1f38536
Timestamp: 1704235890 Timestamp [UCT]: 2024-01-02 22:51:30 Age [y:d:h:m:s]: 01:161:13:28:36
Block: 926854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376588 RingCT/type: yes/0
Extra: 01b4fe952525b8630426b4c5928e8b8136c0914bf0737e5925dc7167fdc1f385360211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eca3d8caa22345130f55b1744f831612550d1b49482931d72c23371938d6f53e 0.600000000000 1384652 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": 926864, "vin": [ { "gen": { "height": 926854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eca3d8caa22345130f55b1744f831612550d1b49482931d72c23371938d6f53e" } } ], "extra": [ 1, 180, 254, 149, 37, 37, 184, 99, 4, 38, 180, 197, 146, 142, 139, 129, 54, 192, 145, 75, 240, 115, 126, 89, 37, 220, 113, 103, 253, 193, 243, 133, 54, 2, 17, 0, 0, 0, 3, 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