Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c85936d8a1a2a63adb52def0fbe4551953f73718fb5865159270c9eb74c9849

Tx prefix hash: 1864ea122278576878db3cf4c0326d1bd2f383e11d2ce0eb5ee5299dd8639825
Tx public key: 1b70d2019f1c7ad34b6d9b8457548e1a89d5c0b51bb8c3df32e60cc74af9dac1
Timestamp: 1711816431 Timestamp [UCT]: 2024-03-30 16:33:51 Age [y:d:h:m:s]: 01:047:15:32:47
Block: 989725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295030 RingCT/type: yes/0
Extra: 011b70d2019f1c7ad34b6d9b8457548e1a89d5c0b51bb8c3df32e60cc74af9dac10211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a993e68877c2b67d56df6ce59552fe7d8cf44afebf55bcec9052c3864455510d 0.600000000000 1450043 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": 989735, "vin": [ { "gen": { "height": 989725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a993e68877c2b67d56df6ce59552fe7d8cf44afebf55bcec9052c3864455510d" } } ], "extra": [ 1, 27, 112, 210, 1, 159, 28, 122, 211, 75, 109, 155, 132, 87, 84, 142, 26, 137, 213, 192, 181, 27, 184, 195, 223, 50, 230, 12, 199, 74, 249, 218, 193, 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