Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a39a734d6b508f50707376e09003747255f58cce5a8de6ae83f9a027d9775e5d

Tx prefix hash: 039d7b11e874303f8f7394ffd43cb0b5640725606e2d1692525af493ef079a9f
Tx public key: 0d7a87392ca0dc817e710dcb4dc285b565a83ba3003f57db92a3e2d27afb58c2
Timestamp: 1763270299 Timestamp [UCT]: 2025-11-16 05:18:19 Age [y:d:h:m:s]: 00:037:04:39:43
Block: 1413157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26626 RingCT/type: yes/0
Extra: 010d7a87392ca0dc817e710dcb4dc285b565a83ba3003f57db92a3e2d27afb58c202110000000117b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ee074777f03a691901a0c8c32d77d3826fe948b668474d2ce707fbe8d7753cd 0.600000000000 1901634 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": 1413167, "vin": [ { "gen": { "height": 1413157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ee074777f03a691901a0c8c32d77d3826fe948b668474d2ce707fbe8d7753cd" } } ], "extra": [ 1, 13, 122, 135, 57, 44, 160, 220, 129, 126, 113, 13, 203, 77, 194, 133, 181, 101, 168, 59, 163, 0, 63, 87, 219, 146, 163, 226, 210, 122, 251, 88, 194, 2, 17, 0, 0, 0, 1, 23, 177, 145, 50, 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