Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6303f5ad24cc4a6c353ca6e6e025aa2cac0a11c09f9a0b15e3783f71a5b7114

Tx prefix hash: a3e16aebf709a5be12a13dc3dcdaafb9fccaa9e6e5084b8cbdb0ef4f84668208
Tx public key: 0d79fed4e03b2857e491822ca522c118bc85dbda0afcfeb88955615eb1da7a79
Timestamp: 1703459350 Timestamp [UCT]: 2023-12-24 23:09:10 Age [y:d:h:m:s]: 01:103:00:07:07
Block: 920431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334727 RingCT/type: yes/0
Extra: 010d79fed4e03b2857e491822ca522c118bc85dbda0afcfeb88955615eb1da7a790211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a7bb341c5a518894b1b3235ad18287f6a068c634f5bd58ffa87f40df6c7791b 0.600000000000 1378109 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": 920441, "vin": [ { "gen": { "height": 920431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a7bb341c5a518894b1b3235ad18287f6a068c634f5bd58ffa87f40df6c7791b" } } ], "extra": [ 1, 13, 121, 254, 212, 224, 59, 40, 87, 228, 145, 130, 44, 165, 34, 193, 24, 188, 133, 219, 218, 10, 252, 254, 184, 137, 85, 97, 94, 177, 218, 122, 121, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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