Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2fe2f8850d1e83acfd15700c7f54afba1a8e97754ea6119ead7b974c3ce3611

Tx prefix hash: 333a564c48f15f3997a5f95dff7541ed501e39613851ef486adfc3a8ed33be99
Tx public key: 60842f6ad3ff38c35f724230f5e87ae8cbe6e08b717fe193a1fcf34cace83c89
Timestamp: 1722038711 Timestamp [UCT]: 2024-07-27 00:05:11 Age [y:d:h:m:s]: 00:296:07:12:04
Block: 1074453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211702 RingCT/type: yes/0
Extra: 0160842f6ad3ff38c35f724230f5e87ae8cbe6e08b717fe193a1fcf34cace83c89021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62983a95aae39319003c0b36f272fc1f46dab03caaa6510ac1595a6beb6fb989 0.600000000000 1546966 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": 1074463, "vin": [ { "gen": { "height": 1074453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62983a95aae39319003c0b36f272fc1f46dab03caaa6510ac1595a6beb6fb989" } } ], "extra": [ 1, 96, 132, 47, 106, 211, 255, 56, 195, 95, 114, 66, 48, 245, 232, 122, 232, 203, 230, 224, 139, 113, 127, 225, 147, 161, 252, 243, 76, 172, 232, 60, 137, 2, 17, 0, 0, 0, 9, 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