Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59ab518a422395f8a55838bf895229aaa706d9fc04c2260163b0c95ea3608ff0

Tx prefix hash: 464f7d93b42e43b46480b92c62cb7d9cac907060ad200565e58ad726a0315459
Tx public key: 2c6fd99efe7ef04ce4cf93806f78c5ba25effd9ead8764d0cbbf54b332998253
Timestamp: 1577960304 Timestamp [UCT]: 2020-01-02 10:18:24 Age [y:d:h:m:s]: 05:097:15:54:34
Block: 37127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1219536 RingCT/type: yes/0
Extra: 012c6fd99efe7ef04ce4cf93806f78c5ba25effd9ead8764d0cbbf54b33299825302110000001e8a2ee0d9000000000000000000

1 output(s) for total of 462.363655538000 dcy

stealth address amount amount idx
00: 5e5be51348b74e46c310ebaef8fec082730c8d372cc37fe3e52e8db84dd1c87d 462.363655538000 62963 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": 37137, "vin": [ { "gen": { "height": 37127 } } ], "vout": [ { "amount": 462363655538, "target": { "key": "5e5be51348b74e46c310ebaef8fec082730c8d372cc37fe3e52e8db84dd1c87d" } } ], "extra": [ 1, 44, 111, 217, 158, 254, 126, 240, 76, 228, 207, 147, 128, 111, 120, 197, 186, 37, 239, 253, 158, 173, 135, 100, 208, 203, 191, 84, 179, 50, 153, 130, 83, 2, 17, 0, 0, 0, 30, 138, 46, 224, 217, 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