Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae9f0fc01310b97ea238eb2abf1c77d032f954d5bc4286f671701b259d044645

Tx prefix hash: 734d99d20c6617fcc5ccee68628e0d00cd578e1ba80902fb954d46c4442f7b33
Tx public key: 853c399bc8fd6a5230a5940d5938a543740b5b57ea9d0865b5af91b3fc56e109
Timestamp: 1712522119 Timestamp [UCT]: 2024-04-07 20:35:19 Age [y:d:h:m:s]: 01:011:13:47:45
Block: 995528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269256 RingCT/type: yes/0
Extra: 01853c399bc8fd6a5230a5940d5938a543740b5b57ea9d0865b5af91b3fc56e1090211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 512a31a4e4fd5283eb9f122f2029aebfdff27d42012f653270d7f9f1eed9d486 0.600000000000 1455938 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": 995538, "vin": [ { "gen": { "height": 995528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "512a31a4e4fd5283eb9f122f2029aebfdff27d42012f653270d7f9f1eed9d486" } } ], "extra": [ 1, 133, 60, 57, 155, 200, 253, 106, 82, 48, 165, 148, 13, 89, 56, 165, 67, 116, 11, 91, 87, 234, 157, 8, 101, 181, 175, 145, 179, 252, 86, 225, 9, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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