Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a4fd73ac369171bf083fb1412ba9dde2450c93f0c18c2e5c33f72de4b6c6a24

Tx prefix hash: d7938f65ca9f71f43d1e44d10c776a9d1c0bf440bd0aa6bb52b55fbb0ec180e3
Tx public key: 8aabbf652bbe18b4b0601e95e96957ff99b4f293884c3d587afd2caf624defa2
Timestamp: 1714390824 Timestamp [UCT]: 2024-04-29 11:40:24 Age [y:d:h:m:s]: 00:255:02:00:48
Block: 1011051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182584 RingCT/type: yes/0
Extra: 018aabbf652bbe18b4b0601e95e96957ff99b4f293884c3d587afd2caf624defa20211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27c9e8220f60f8609207699d8378a033778598f18301fd0ce791e3b5135f7e67 0.600000000000 1473175 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": 1011061, "vin": [ { "gen": { "height": 1011051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27c9e8220f60f8609207699d8378a033778598f18301fd0ce791e3b5135f7e67" } } ], "extra": [ 1, 138, 171, 191, 101, 43, 190, 24, 180, 176, 96, 30, 149, 233, 105, 87, 255, 153, 180, 242, 147, 136, 76, 61, 88, 122, 253, 44, 175, 98, 77, 239, 162, 2, 17, 0, 0, 0, 5, 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