Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bd9b5e3daf4375e160523961a363e9878db45c35a5e77be0d202189c22a9f27

Tx prefix hash: de448b8699d43c58808600a9446ac3de15016962651cbd3987382ebce8c9a125
Tx public key: 830750d8f09c3c0e14f7824f5a64ae6eace343a9f9c937fe978d61b9dd3f4a02
Timestamp: 1728672945 Timestamp [UCT]: 2024-10-11 18:55:45 Age [y:d:h:m:s]: 00:184:18:45:35
Block: 1129462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131849 RingCT/type: yes/0
Extra: 01830750d8f09c3c0e14f7824f5a64ae6eace343a9f9c937fe978d61b9dd3f4a02021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 807a7098d8ce37c04d71791cce70cb8b6544bbef667d5546294b9e2389708db0 0.600000000000 1612289 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": 1129472, "vin": [ { "gen": { "height": 1129462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "807a7098d8ce37c04d71791cce70cb8b6544bbef667d5546294b9e2389708db0" } } ], "extra": [ 1, 131, 7, 80, 216, 240, 156, 60, 14, 20, 247, 130, 79, 90, 100, 174, 110, 172, 227, 67, 169, 249, 201, 55, 254, 151, 141, 97, 185, 221, 63, 74, 2, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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