Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3c098a0db96fcf48a39139e766281c141f00ee570a3893e024814f8d3d5ae80

Tx prefix hash: 96fcd8609b1a6f9382e1a973c8c040bb7fd28b47547499f33650043ebc603e45
Tx public key: 63562c6f1b79a31d339b9bec18caa2d352178c928500054493b62bd9a2b3009e
Timestamp: 1713189736 Timestamp [UCT]: 2024-04-15 14:02:16 Age [y:d:h:m:s]: 01:039:21:36:10
Block: 1001086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289500 RingCT/type: yes/0
Extra: 0163562c6f1b79a31d339b9bec18caa2d352178c928500054493b62bd9a2b3009e0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce555724055bced2a7d2b5bcf90efc44731c3464cb08a192aae46e9369e974f0 0.600000000000 1461588 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": 1001096, "vin": [ { "gen": { "height": 1001086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce555724055bced2a7d2b5bcf90efc44731c3464cb08a192aae46e9369e974f0" } } ], "extra": [ 1, 99, 86, 44, 111, 27, 121, 163, 29, 51, 155, 155, 236, 24, 202, 162, 211, 82, 23, 140, 146, 133, 0, 5, 68, 147, 182, 43, 217, 162, 179, 0, 158, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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