Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4007f8cc0d0ffa7e1a6fd53fcfb9e90d64d00d62bddfa360e87a1a20b575f47f

Tx prefix hash: bb4a228bb606569eebe83f062ac23f83e335fb838ff80697091ac73a6cd74010
Tx public key: ea4634affecf6b911147ce3877f4ff2de5be0a5f81bb703986571aab6d77ae70
Timestamp: 1761755142 Timestamp [UCT]: 2025-10-29 16:25:42 Age [y:d:h:m:s]: 00:060:16:12:32
Block: 1400615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43433 RingCT/type: yes/0
Extra: 01ea4634affecf6b911147ce3877f4ff2de5be0a5f81bb703986571aab6d77ae700211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b540d614e055e5af75e7c5d71a6aa569c6af14b3c6b0f0b0f91721368018582 0.600000000000 1888932 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": 1400625, "vin": [ { "gen": { "height": 1400615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b540d614e055e5af75e7c5d71a6aa569c6af14b3c6b0f0b0f91721368018582" } } ], "extra": [ 1, 234, 70, 52, 175, 254, 207, 107, 145, 17, 71, 206, 56, 119, 244, 255, 45, 229, 190, 10, 95, 129, 187, 112, 57, 134, 87, 26, 171, 109, 119, 174, 112, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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