Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a95f2eb151a5aeabb02a02a442d158f97a07053e8133ef036df5333755067cac

Tx prefix hash: 69f4389fcc56ecfe88e508a76efcf8bf4ff1692cf5c1ca596998063400cfbea8
Tx public key: 24ae863453ac19c093b6ae0bf8bd80fff227806cec3b4773e32b0dfc51d1c0df
Timestamp: 1749479705 Timestamp [UCT]: 2025-06-09 14:35:05 Age [y:d:h:m:s]: 00:154:05:10:37
Block: 1301416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107882 RingCT/type: yes/0
Extra: 0124ae863453ac19c093b6ae0bf8bd80fff227806cec3b4773e32b0dfc51d1c0df021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ab11adcb5c25f10cee722308032d3cc0c693159cfb8e53191a4a439c2f1ebf0 0.600000000000 1788975 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": 1301426, "vin": [ { "gen": { "height": 1301416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ab11adcb5c25f10cee722308032d3cc0c693159cfb8e53191a4a439c2f1ebf0" } } ], "extra": [ 1, 36, 174, 134, 52, 83, 172, 25, 192, 147, 182, 174, 11, 248, 189, 128, 255, 242, 39, 128, 108, 236, 59, 71, 115, 227, 43, 13, 252, 81, 209, 192, 223, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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