Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b5c5fba1791bcf0c4e5649156a29c2978dc26b1f5f8ee08e54224fdc0d85dfe

Tx prefix hash: 42395760fccd1e648f0d8850aef42a9b2ca16ea1c22bb39769b0023f889adc8e
Tx public key: 016d44ebc7e87b74ed6e3f3b2f55f3c1981d918b53681d3fdebfa4a5c8ad55c9
Timestamp: 1761905601 Timestamp [UCT]: 2025-10-31 10:13:21 Age [y:d:h:m:s]: 00:027:20:38:45
Block: 1401867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19933 RingCT/type: yes/0
Extra: 01016d44ebc7e87b74ed6e3f3b2f55f3c1981d918b53681d3fdebfa4a5c8ad55c902110000000525a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd39806617f231f0816d27dca64d9c95c337d777a8a052d0e90462a6a754d36c 0.600000000000 1890186 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": 1401877, "vin": [ { "gen": { "height": 1401867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd39806617f231f0816d27dca64d9c95c337d777a8a052d0e90462a6a754d36c" } } ], "extra": [ 1, 1, 109, 68, 235, 199, 232, 123, 116, 237, 110, 63, 59, 47, 85, 243, 193, 152, 29, 145, 139, 83, 104, 29, 63, 222, 191, 164, 165, 200, 173, 85, 201, 2, 17, 0, 0, 0, 5, 37, 163, 90, 15, 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