Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2afe7a345af6fa6ac46b58af153807e1dd4e63e0b9c7c547c42ede584af9ca28

Tx prefix hash: 0be49dd3bb48e24dd1cf5a4186ce41081ad37a94cc2e9e2bb49f0ddc9617e9c1
Tx public key: 7295fe10b756329ce40f63c54ddda7914033fd99cc9787d927c7c6297fa9c913
Timestamp: 1736020580 Timestamp [UCT]: 2025-01-04 19:56:20 Age [y:d:h:m:s]: 00:350:21:31:46
Block: 1190241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248345 RingCT/type: yes/0
Extra: 017295fe10b756329ce40f63c54ddda7914033fd99cc9787d927c7c6297fa9c913021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 615645b0e3c564edd89e96e263d10975eb43dc847a5a80d2dbb7a2c23d9fefcd 0.600000000000 1676756 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": 1190251, "vin": [ { "gen": { "height": 1190241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "615645b0e3c564edd89e96e263d10975eb43dc847a5a80d2dbb7a2c23d9fefcd" } } ], "extra": [ 1, 114, 149, 254, 16, 183, 86, 50, 156, 228, 15, 99, 197, 77, 221, 167, 145, 64, 51, 253, 153, 204, 151, 135, 217, 39, 199, 198, 41, 127, 169, 201, 19, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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