Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 562ba2d3206b3bd13c67dd769d2425c0a6352046906b6ecbf8055d2668439d5e

Tx prefix hash: ab8178f8f3c28ab1567bf87d3f4f6ed5491379999188201eb3343bfdf3b5b8ef
Tx public key: 76b867f5160a0d8827a3221f5b56c22a2dcdde3b76ddaa397d13df7355a2d56c
Timestamp: 1725182891 Timestamp [UCT]: 2024-09-01 09:28:11 Age [y:d:h:m:s]: 00:222:11:47:02
Block: 1100525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158874 RingCT/type: yes/0
Extra: 0176b867f5160a0d8827a3221f5b56c22a2dcdde3b76ddaa397d13df7355a2d56c021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f08cb290fb4fcbf8fe1ac4cd6a8e4b6e8407f9bf9f8894a851296895b39eb203 0.600000000000 1576504 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": 1100535, "vin": [ { "gen": { "height": 1100525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f08cb290fb4fcbf8fe1ac4cd6a8e4b6e8407f9bf9f8894a851296895b39eb203" } } ], "extra": [ 1, 118, 184, 103, 245, 22, 10, 13, 136, 39, 163, 34, 31, 91, 86, 194, 42, 45, 205, 222, 59, 118, 221, 170, 57, 125, 19, 223, 115, 85, 162, 213, 108, 2, 17, 0, 0, 0, 9, 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