Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af49a02990b8c1fa0f8a95197e90808710ad0a195204c46f25e3e3dba9ead559

Tx prefix hash: b24d4e17028aea9a60a4edea33b61d198007e1c2d6c4bf41cab01ef2a02ddde6
Tx public key: 96af56713fb0fbd39b229c6613a149e334d095891c216c80343efb1c97d700df
Timestamp: 1723595970 Timestamp [UCT]: 2024-08-14 00:39:30 Age [y:d:h:m:s]: 01:082:04:22:08
Block: 1087370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317190 RingCT/type: yes/0
Extra: 0196af56713fb0fbd39b229c6613a149e334d095891c216c80343efb1c97d700df021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13a2ba7f5d6db5b92e89e2fbd34e444baadbd3c971d2d29e20266cfe6ef8b6cd 0.600000000000 1561979 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": 1087380, "vin": [ { "gen": { "height": 1087370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13a2ba7f5d6db5b92e89e2fbd34e444baadbd3c971d2d29e20266cfe6ef8b6cd" } } ], "extra": [ 1, 150, 175, 86, 113, 63, 176, 251, 211, 155, 34, 156, 102, 19, 161, 73, 227, 52, 208, 149, 137, 28, 33, 108, 128, 52, 62, 251, 28, 151, 215, 0, 223, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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