Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df70fe209231b33ae97d18741ca73934d8ff1c490e0dc7ecd0e98124b7d8a5f6

Tx prefix hash: a66df7e293a13c1b0fe4d7a81693650e83321087e229321f573450217e605257
Tx public key: ba41c34e49258c0c0a210cb55cb52806e461eb95ffa892f1edc13f1214215a44
Timestamp: 1756111696 Timestamp [UCT]: 2025-08-25 08:48:16 Age [y:d:h:m:s]: 00:087:22:57:23
Block: 1354019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62781 RingCT/type: yes/0
Extra: 01ba41c34e49258c0c0a210cb55cb52806e461eb95ffa892f1edc13f1214215a440211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9f2aa4abc12f4a6259a89ad63f1430d76f0ba01b101770a4a8c628f5d29249f 0.600000000000 1842000 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": 1354029, "vin": [ { "gen": { "height": 1354019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9f2aa4abc12f4a6259a89ad63f1430d76f0ba01b101770a4a8c628f5d29249f" } } ], "extra": [ 1, 186, 65, 195, 78, 73, 37, 140, 12, 10, 33, 12, 181, 92, 181, 40, 6, 228, 97, 235, 149, 255, 168, 146, 241, 237, 193, 63, 18, 20, 33, 90, 68, 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