Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b61ad038b05d4270ae04bdf9fd25e60bb5cac58fec724a71233c24b6a8664ef1

Tx prefix hash: 04363b39bdd3acdf2e754072b839c6421e4fd6b1f98de4f7b602647dae9baa90
Tx public key: e39eb2e7d23a14b7964da25edbd8261f75e823a1501ccc874a6d608b11424392
Timestamp: 1724457991 Timestamp [UCT]: 2024-08-24 00:06:31 Age [y:d:h:m:s]: 01:160:18:46:43
Block: 1094526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373271 RingCT/type: yes/0
Extra: 01e39eb2e7d23a14b7964da25edbd8261f75e823a1501ccc874a6d608b1142439202110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e81109a3f0a81bc9f6382c3ba2ef1a26481679a1a88d69e78382788aa2fd40d9 0.600000000000 1569643 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": 1094536, "vin": [ { "gen": { "height": 1094526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e81109a3f0a81bc9f6382c3ba2ef1a26481679a1a88d69e78382788aa2fd40d9" } } ], "extra": [ 1, 227, 158, 178, 231, 210, 58, 20, 183, 150, 77, 162, 94, 219, 216, 38, 31, 117, 232, 35, 161, 80, 28, 204, 135, 74, 109, 96, 139, 17, 66, 67, 146, 2, 17, 0, 0, 0, 14, 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