Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ea1fe9b0d27d40aebca74ccfe8dfbdbe271b953a517f9d179e0664520ce3d86

Tx prefix hash: ddd1c38699287ff1fc937fa589b25054b27e0e86243d298979c37e4e130d3905
Tx public key: e41db30f830db74efc32e52e497a9e43c3ae559742b51e7abb3d079350e5b6a7
Timestamp: 1708306842 Timestamp [UCT]: 2024-02-19 01:40:42 Age [y:d:h:m:s]: 00:266:08:20:42
Block: 960612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190684 RingCT/type: yes/0
Extra: 01e41db30f830db74efc32e52e497a9e43c3ae559742b51e7abb3d079350e5b6a70211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 157633710da5e06d4200f928e488e77c8105e545513dcd39eb975ac7f10efa63 0.600000000000 1420197 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": 960622, "vin": [ { "gen": { "height": 960612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "157633710da5e06d4200f928e488e77c8105e545513dcd39eb975ac7f10efa63" } } ], "extra": [ 1, 228, 29, 179, 15, 131, 13, 183, 78, 252, 50, 229, 46, 73, 122, 158, 67, 195, 174, 85, 151, 66, 181, 30, 122, 187, 61, 7, 147, 80, 229, 182, 167, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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