Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6a514aac3b3cf3732d6eee50eaff29733e07759e4b01e55aa07c30164129c43

Tx prefix hash: 0cb998b718fc0bb0dff489dfe7a87fc0236f50ab98aa6ace45c73eb4c027c31b
Tx public key: ae4a399a1fc8e947712955ef2ea7b486e588004cffb18bd093ec8e2296d58c0b
Timestamp: 1761162022 Timestamp [UCT]: 2025-10-22 19:40:22 Age [y:d:h:m:s]: 00:029:22:10:14
Block: 1395701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21404 RingCT/type: yes/0
Extra: 01ae4a399a1fc8e947712955ef2ea7b486e588004cffb18bd093ec8e2296d58c0b021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9c8fb4ad4c1752b67b2ee60d4c536964b3209783ad4332cfe5298ce2c7e48dd 0.600000000000 1883984 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": 1395711, "vin": [ { "gen": { "height": 1395701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9c8fb4ad4c1752b67b2ee60d4c536964b3209783ad4332cfe5298ce2c7e48dd" } } ], "extra": [ 1, 174, 74, 57, 154, 31, 200, 233, 71, 113, 41, 85, 239, 46, 167, 180, 134, 229, 136, 0, 76, 255, 177, 139, 208, 147, 236, 142, 34, 150, 213, 140, 11, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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