Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f16a277df223373bf2e97f4cd901fed7be251cb54fdfa99afa6859163b67880c

Tx prefix hash: a9f393f54a86422f411254cea43bb640125be1be2f2a538e25367ea19aee810e
Tx public key: dec88d5f5ef6801eb3d30d01caf72f1a24e315342e54882e2b8c42a4a83a2e87
Timestamp: 1751675536 Timestamp [UCT]: 2025-07-05 00:32:16 Age [y:d:h:m:s]: 00:128:03:39:57
Block: 1318927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89909 RingCT/type: yes/0
Extra: 01dec88d5f5ef6801eb3d30d01caf72f1a24e315342e54882e2b8c42a4a83a2e8702110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 603d11f5b5a6ac9c188d79b1e3fc3360aa8a90504d689d68baa85f7a3207aaa9 0.600000000000 1806614 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": 1318937, "vin": [ { "gen": { "height": 1318927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "603d11f5b5a6ac9c188d79b1e3fc3360aa8a90504d689d68baa85f7a3207aaa9" } } ], "extra": [ 1, 222, 200, 141, 95, 94, 246, 128, 30, 179, 211, 13, 1, 202, 247, 47, 26, 36, 227, 21, 52, 46, 84, 136, 46, 43, 140, 66, 164, 168, 58, 46, 135, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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