Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a30fd66cf6fa564c03abe2b8d683473d3e0f82bc7a84a1115485a2509ffda8fd

Tx prefix hash: cfd4c67b7cdd65632782aa5265b78a79ade1bd8a0be279c40e20e4b1f25b655f
Tx public key: ad5cc1f123d7fae0576d72bcff0f51cacefefa7308b25a48470d134698b5024b
Timestamp: 1706736735 Timestamp [UCT]: 2024-01-31 21:32:15 Age [y:d:h:m:s]: 01:142:07:15:41
Block: 947575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362646 RingCT/type: yes/0
Extra: 01ad5cc1f123d7fae0576d72bcff0f51cacefefa7308b25a48470d134698b5024b02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29b4150b61a8c922c6fc89c96f4bef9e39b231dc467efdca4913526b8b1b3dc7 0.600000000000 1405927 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": 947585, "vin": [ { "gen": { "height": 947575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29b4150b61a8c922c6fc89c96f4bef9e39b231dc467efdca4913526b8b1b3dc7" } } ], "extra": [ 1, 173, 92, 193, 241, 35, 215, 250, 224, 87, 109, 114, 188, 255, 15, 81, 202, 206, 254, 250, 115, 8, 178, 90, 72, 71, 13, 19, 70, 152, 181, 2, 75, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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