Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dabc04bb79e8fc0e65b5c42999111557828e902250c8263cf687b606882e539

Tx prefix hash: 09aecdab9299045e73fd01061b21d999aa2284caa4ce02d60fa23ffb85787b5f
Tx public key: d486ec5f4a5e83ac564d1c4e8943a30f4ca0734e6a6255844901b18d26f39f5e
Timestamp: 1697003195 Timestamp [UCT]: 2023-10-11 05:46:35 Age [y:d:h:m:s]: 01:179:13:26:15
Block: 867103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389356 RingCT/type: yes/0
Extra: 01d486ec5f4a5e83ac564d1c4e8943a30f4ca0734e6a6255844901b18d26f39f5e02110000000a4b8f5122000000000000000000

1 output(s) for total of 0.822106044000 dcy

stealth address amount amount idx
00: 9f6e957df56ce8157ca425907e3e8abdcb1a0f9ec0700867a0012d54e1ad3680 0.822106044000 1321755 of 0

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": 867113, "vin": [ { "gen": { "height": 867103 } } ], "vout": [ { "amount": 822106044, "target": { "key": "9f6e957df56ce8157ca425907e3e8abdcb1a0f9ec0700867a0012d54e1ad3680" } } ], "extra": [ 1, 212, 134, 236, 95, 74, 94, 131, 172, 86, 77, 28, 78, 137, 67, 163, 15, 76, 160, 115, 78, 106, 98, 85, 132, 73, 1, 177, 141, 38, 243, 159, 94, 2, 17, 0, 0, 0, 10, 75, 143, 81, 34, 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