Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01601f95cd42a572f5c3cf8929ed9f130e31148ee8baa94c555cff0546418bcb

Tx prefix hash: 01dd6778a8f9e453c5f5ada17ad05e2476717335486ab3257e2f3f9dc8b0ec22
Tx public key: a0ea6b2db05609d7c682ef4bc7a9f4da1e876c0f687979f6684e9b36b80a9331
Timestamp: 1731693265 Timestamp [UCT]: 2024-11-15 17:54:25 Age [y:d:h:m:s]: 00:218:19:50:10
Block: 1154392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156086 RingCT/type: yes/0
Extra: 01a0ea6b2db05609d7c682ef4bc7a9f4da1e876c0f687979f6684e9b36b80a9331021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 952dca815adb4d722e39fc2332ba5c021e141f87136fb9d64abc9d75253bebe4 0.600000000000 1640003 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": 1154402, "vin": [ { "gen": { "height": 1154392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "952dca815adb4d722e39fc2332ba5c021e141f87136fb9d64abc9d75253bebe4" } } ], "extra": [ 1, 160, 234, 107, 45, 176, 86, 9, 215, 198, 130, 239, 75, 199, 169, 244, 218, 30, 135, 108, 15, 104, 121, 121, 246, 104, 78, 155, 54, 184, 10, 147, 49, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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