Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5a5cec5d574b879e5d286763d8fab4db1d9681aa010c8cdff36cf53e1818887

Tx prefix hash: 0f9799a7cf5ff684c43dbede73b7025708668b1f81835db1cab5e9083240aeef
Tx public key: 498f858ed310e7854ecbdbccab592af2cfe4004f6fbeaa1f4068110fd17655e1
Timestamp: 1582512258 Timestamp [UCT]: 2020-02-24 02:44:18 Age [y:d:h:m:s]: 05:082:06:53:51
Block: 71238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1212128 RingCT/type: yes/0
Extra: 01498f858ed310e7854ecbdbccab592af2cfe4004f6fbeaa1f4068110fd17655e10211000000017adf42d3000000000000000000

1 output(s) for total of 356.471497558000 dcy

stealth address amount amount idx
00: 014e9c3c3bde88a62bebb7f6f1a434051cce05d4ec26e9890ea6fe223ea55e84 356.471497558000 131628 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": 71248, "vin": [ { "gen": { "height": 71238 } } ], "vout": [ { "amount": 356471497558, "target": { "key": "014e9c3c3bde88a62bebb7f6f1a434051cce05d4ec26e9890ea6fe223ea55e84" } } ], "extra": [ 1, 73, 143, 133, 142, 211, 16, 231, 133, 78, 203, 219, 204, 171, 89, 42, 242, 207, 228, 0, 79, 111, 190, 170, 31, 64, 104, 17, 15, 209, 118, 85, 225, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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