Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b1e16c9caaa19fb4369bdb1f6251cfb80d93b2382f2a0822669df7db3a1da58

Tx prefix hash: 1bd54551264e219edb84893a47d2acdb55ad45b3f427ecd79d03283564168d94
Tx public key: abaf861c4bd20f805e17519c65c46edeb96b3d18b7adc5db4e0ba1ed12e74092
Timestamp: 1698106820 Timestamp [UCT]: 2023-10-24 00:20:20 Age [y:d:h:m:s]: 01:143:17:55:31
Block: 876250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363765 RingCT/type: yes/0
Extra: 01abaf861c4bd20f805e17519c65c46edeb96b3d18b7adc5db4e0ba1ed12e7409202110000000de6d27f9c000000000000000000

1 output(s) for total of 0.766690390000 dcy

stealth address amount amount idx
00: 167e80576eb5d380bba44583945af54dd256b0ece90a09ba8b3cb2ba660d77e8 0.766690390000 1331568 of 0

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": 876260, "vin": [ { "gen": { "height": 876250 } } ], "vout": [ { "amount": 766690390, "target": { "key": "167e80576eb5d380bba44583945af54dd256b0ece90a09ba8b3cb2ba660d77e8" } } ], "extra": [ 1, 171, 175, 134, 28, 75, 210, 15, 128, 94, 23, 81, 156, 101, 196, 110, 222, 185, 107, 61, 24, 183, 173, 197, 219, 78, 11, 161, 237, 18, 231, 64, 146, 2, 17, 0, 0, 0, 13, 230, 210, 127, 156, 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