Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9d20fe821e146710cafff3b79c948c084dce5d18c36d085d14fb7b48721f93b

Tx prefix hash: 5fde49c5706abeb5b35e9b9e9d8a3d7d5e67ef86cfc2d9d68ea0110a1564fb56
Tx public key: 6f98b5b3513f05691a83e568dfc0c0ac6b57b632a10ef4a3b52c9c43e426cfbd
Timestamp: 1730510029 Timestamp [UCT]: 2024-11-02 01:13:49 Age [y:d:h:m:s]: 00:136:05:24:34
Block: 1144599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97196 RingCT/type: yes/0
Extra: 016f98b5b3513f05691a83e568dfc0c0ac6b57b632a10ef4a3b52c9c43e426cfbd021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e6a50059c5fa0733f54fc700591473d7563a8517d2d65f644ecd73a51842442 0.600000000000 1628862 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": 1144609, "vin": [ { "gen": { "height": 1144599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e6a50059c5fa0733f54fc700591473d7563a8517d2d65f644ecd73a51842442" } } ], "extra": [ 1, 111, 152, 181, 179, 81, 63, 5, 105, 26, 131, 229, 104, 223, 192, 192, 172, 107, 87, 182, 50, 161, 14, 244, 163, 181, 44, 156, 67, 228, 38, 207, 189, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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