Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d63658ff7b988245ba391ae2d6b2d33dd71bb433e3fc78abe7fbc0b336a25a1

Tx prefix hash: ad420bc5b11a473f37ae384020c023a7752da4186cabbc711cc29f6114ef5ef3
Tx public key: 2d5f279d8b82ac2ef086dc29aae2b941c755a7b5edda6b0933100a0a146cc242
Timestamp: 1755404261 Timestamp [UCT]: 2025-08-17 04:17:41 Age [y:d:h:m:s]: 00:044:14:57:38
Block: 1348264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31650 RingCT/type: yes/0
Extra: 012d5f279d8b82ac2ef086dc29aae2b941c755a7b5edda6b0933100a0a146cc242021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10f6d849194885b741086e44a0a666f92bd6d44ace0eac0f5100792b8ce549cf 0.600000000000 1836189 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": 1348274, "vin": [ { "gen": { "height": 1348264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10f6d849194885b741086e44a0a666f92bd6d44ace0eac0f5100792b8ce549cf" } } ], "extra": [ 1, 45, 95, 39, 157, 139, 130, 172, 46, 240, 134, 220, 41, 170, 226, 185, 65, 199, 85, 167, 181, 237, 218, 107, 9, 51, 16, 10, 10, 20, 108, 194, 66, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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