Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86d4fdd8aeccf1d108934723820cfb23ae99e9f0aec1d57a01c613cb68a25da2

Tx prefix hash: 3b4eb6b1ebecb5d9dd92712272ca2981dc3bf6c37617aff8620e47737b723417
Tx public key: a8ef0a56e337f9c8cd09c5c1d4b700f9b3be7eb208806b15f3d3421b2f9f347e
Timestamp: 1674613740 Timestamp [UCT]: 2023-01-25 02:29:00 Age [y:d:h:m:s]: 02:077:00:46:36
Block: 682160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 576703 RingCT/type: yes/0
Extra: 01a8ef0a56e337f9c8cd09c5c1d4b700f9b3be7eb208806b15f3d3421b2f9f347e0211000000025029cbac000000000000000000

1 output(s) for total of 3.370704504000 dcy

stealth address amount amount idx
00: 1a9bdf71445de9df2bb310ff4fdc2f92a5e000bc62ef1dd5f1787e65db0c46c3 3.370704504000 1124275 of 0

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": 682170, "vin": [ { "gen": { "height": 682160 } } ], "vout": [ { "amount": 3370704504, "target": { "key": "1a9bdf71445de9df2bb310ff4fdc2f92a5e000bc62ef1dd5f1787e65db0c46c3" } } ], "extra": [ 1, 168, 239, 10, 86, 227, 55, 249, 200, 205, 9, 197, 193, 212, 183, 0, 249, 179, 190, 126, 178, 8, 128, 107, 21, 243, 211, 66, 27, 47, 159, 52, 126, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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