Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c401723150d2f8fc595ec4b5f45c2ec9207506c47e7ced9c73803b1434aee791

Tx prefix hash: f85dd40ee14ca38e5590244d41cd6e3b994c813c2739f2f29894bbf7b173082d
Tx public key: bf9d5adf2a0c4e17fff6ddb87e2741b67fe348995784f44329251a5901283b00
Timestamp: 1729528064 Timestamp [UCT]: 2024-10-21 16:27:44 Age [y:d:h:m:s]: 00:001:13:55:09
Block: 1136501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1142 RingCT/type: yes/0
Extra: 01bf9d5adf2a0c4e17fff6ddb87e2741b67fe348995784f44329251a5901283b000211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d439fbf69d9dcb07e11fe272e3e4a3fed406cdd7ee8e71e58e36a83aa51012b 0.600000000000 1619846 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": 1136511, "vin": [ { "gen": { "height": 1136501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d439fbf69d9dcb07e11fe272e3e4a3fed406cdd7ee8e71e58e36a83aa51012b" } } ], "extra": [ 1, 191, 157, 90, 223, 42, 12, 78, 23, 255, 246, 221, 184, 126, 39, 65, 182, 127, 227, 72, 153, 87, 132, 244, 67, 41, 37, 26, 89, 1, 40, 59, 0, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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