Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26ff8700193af8c84d575ac6fc72711a1e96e0c1921c288a9d616aca91dc58df

Tx prefix hash: 4139a40388c02c6c32a6cb3da41674bb62b74b4f5235a19c06280d5610465c40
Tx public key: 87464d552865aa105cfef663ad808cf1f8ca283ca08cbdc91d4f6eeea3862a8c
Timestamp: 1592760676 Timestamp [UCT]: 2020-06-21 17:31:16 Age [y:d:h:m:s]: 04:232:13:25:52
Block: 110091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104529 RingCT/type: yes/0
Extra: 0187464d552865aa105cfef663ad808cf1f8ca283ca08cbdc91d4f6eeea3862a8c02110000000446a11e8a000000000000000000

1 output(s) for total of 264.986387135000 dcy

stealth address amount amount idx
00: 14620a6752fe7e6ba333847d13bc2604603bf9b6a24cf3c9d3db2847b978de1d 264.986387135000 190715 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": 110101, "vin": [ { "gen": { "height": 110091 } } ], "vout": [ { "amount": 264986387135, "target": { "key": "14620a6752fe7e6ba333847d13bc2604603bf9b6a24cf3c9d3db2847b978de1d" } } ], "extra": [ 1, 135, 70, 77, 85, 40, 101, 170, 16, 92, 254, 246, 99, 173, 128, 140, 241, 248, 202, 40, 60, 160, 140, 189, 201, 29, 79, 110, 238, 163, 134, 42, 140, 2, 17, 0, 0, 0, 4, 70, 161, 30, 138, 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