Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e8accfa7a56011f0030c68041026d71ac27a8c8fa19c0091b2745ceee8b1da0

Tx prefix hash: d20e5e6e34f2fa734395965f6c517dc048da45fa8978c9e648cec169addded5f
Tx public key: c219345c972f6babd49ee85099c80525b1ae813804a921e0a2a1b9ff390beff2
Timestamp: 1735033098 Timestamp [UCT]: 2024-12-24 09:38:18 Age [y:d:h:m:s]: 00:097:04:02:22
Block: 1182079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69218 RingCT/type: yes/0
Extra: 01c219345c972f6babd49ee85099c80525b1ae813804a921e0a2a1b9ff390beff20211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb90161ec108d47764e0e6e2736df8e7afc13114ca830d5ac6f2f599ec8fa2d9 0.600000000000 1668510 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": 1182089, "vin": [ { "gen": { "height": 1182079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb90161ec108d47764e0e6e2736df8e7afc13114ca830d5ac6f2f599ec8fa2d9" } } ], "extra": [ 1, 194, 25, 52, 92, 151, 47, 107, 171, 212, 158, 232, 80, 153, 200, 5, 37, 177, 174, 129, 56, 4, 169, 33, 224, 162, 161, 185, 255, 57, 11, 239, 242, 2, 17, 0, 0, 0, 4, 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