Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6203abf5ecb17d771ec6a1c014af25cb3377c208fd0d41209e14258c2af8ea0c

Tx prefix hash: c81ab5819caf78fc97025f36c8b86d3abb6e84edc7849a2ad5d19b992cc61b3b
Tx public key: e286c13d7c78755bda8261e524eece5249cef0aa77b8f7160c6fcfeb3752bd71
Timestamp: 1756143194 Timestamp [UCT]: 2025-08-25 17:33:14 Age [y:d:h:m:s]: 00:085:09:22:49
Block: 1354285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60952 RingCT/type: yes/0
Extra: 01e286c13d7c78755bda8261e524eece5249cef0aa77b8f7160c6fcfeb3752bd710211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b393fcad163fbeae1dda8355c1258eeb72d73d700382b0d8176629bfb964cd6f 0.600000000000 1842272 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": 1354295, "vin": [ { "gen": { "height": 1354285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b393fcad163fbeae1dda8355c1258eeb72d73d700382b0d8176629bfb964cd6f" } } ], "extra": [ 1, 226, 134, 193, 61, 124, 120, 117, 91, 218, 130, 97, 229, 36, 238, 206, 82, 73, 206, 240, 170, 119, 184, 247, 22, 12, 111, 207, 235, 55, 82, 189, 113, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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