Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 939cafa8f29f7298c32c7b5a55a84c003742aa9e39117cc8c8f5e85e5e05a0b0

Tx prefix hash: ef8d85ae29b87101bd5039568451102b41d5be199a2e223e77dca4dc90b10efd
Tx public key: 0a5d9fd36aaefc53e87410cf99d45a2775245ba4dd6cbc2ca72fd197e1307667
Timestamp: 1713522619 Timestamp [UCT]: 2024-04-19 10:30:19 Age [y:d:h:m:s]: 00:353:06:21:30
Block: 1003854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252534 RingCT/type: yes/0
Extra: 010a5d9fd36aaefc53e87410cf99d45a2775245ba4dd6cbc2ca72fd197e1307667021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e2ce3b3e83d92dcee5cc6e293265ad5bc7e340cae3f2f354432382ec05ccda4 0.600000000000 1464400 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": 1003864, "vin": [ { "gen": { "height": 1003854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e2ce3b3e83d92dcee5cc6e293265ad5bc7e340cae3f2f354432382ec05ccda4" } } ], "extra": [ 1, 10, 93, 159, 211, 106, 174, 252, 83, 232, 116, 16, 207, 153, 212, 90, 39, 117, 36, 91, 164, 221, 108, 188, 44, 167, 47, 209, 151, 225, 48, 118, 103, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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