Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca54e41da87558a5b4ea7baddc50fdee1cbec11c54455f26fd5b87b9a20d2b9b

Tx prefix hash: 7829617430570a0a18d10d562d11512bcf2415a09a588701fd61c23fefb533c9
Tx public key: c403c580ada4c2ef948d0dedf5476623ad0b1cd2bfe6971a28871628b71978f4
Timestamp: 1702660597 Timestamp [UCT]: 2023-12-15 17:16:37 Age [y:d:h:m:s]: 01:329:20:47:38
Block: 913799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494615 RingCT/type: yes/0
Extra: 01c403c580ada4c2ef948d0dedf5476623ad0b1cd2bfe6971a28871628b71978f402110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5510db82fd0057d5037b264e0fc85721f065ef2be1ae6eebe44a266f9c6bb98f 0.600000000000 1371077 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": 913809, "vin": [ { "gen": { "height": 913799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5510db82fd0057d5037b264e0fc85721f065ef2be1ae6eebe44a266f9c6bb98f" } } ], "extra": [ 1, 196, 3, 197, 128, 173, 164, 194, 239, 148, 141, 13, 237, 245, 71, 102, 35, 173, 11, 28, 210, 191, 230, 151, 26, 40, 135, 22, 40, 183, 25, 120, 244, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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