Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa361dca0edfed3499f30a68989830ceb2981fa417ffa1fa965645fc5f24c2b2

Tx prefix hash: f519d9f9202b223c2a93efe05f9a26f8021b3d4f0bdb32a64b7a0b331be28655
Tx public key: c9a0fe3aa0e4f3baf8627de254abb44617c34c640abc9fe38220ff164dc5e126
Timestamp: 1719785667 Timestamp [UCT]: 2024-06-30 22:14:27 Age [y:d:h:m:s]: 01:129:02:39:53
Block: 1055770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350806 RingCT/type: yes/0
Extra: 01c9a0fe3aa0e4f3baf8627de254abb44617c34c640abc9fe38220ff164dc5e12602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c55317dce455a15862b83d85cbb362feaeb0c2a4bb1fb9f3eb0109100f85f3b 0.600000000000 1526175 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": 1055780, "vin": [ { "gen": { "height": 1055770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c55317dce455a15862b83d85cbb362feaeb0c2a4bb1fb9f3eb0109100f85f3b" } } ], "extra": [ 1, 201, 160, 254, 58, 160, 228, 243, 186, 248, 98, 125, 226, 84, 171, 180, 70, 23, 195, 76, 100, 10, 188, 159, 227, 130, 32, 255, 22, 77, 197, 225, 38, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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