Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cda57612275df028dc90f0d43ad665ed0f494307d15e7b3af5878dfb9bc34aa5

Tx prefix hash: 62cef93be03e7916286254f406fc3ef0af62bdeb71fa4b872eb1fa2acc8eb46c
Tx public key: d7a2e868e1fead0f8e6a8e7fb4c3d56e3a4ad6c27f40f04306dd927bbdab85b9
Timestamp: 1700260394 Timestamp [UCT]: 2023-11-17 22:33:14 Age [y:d:h:m:s]: 01:179:05:56:32
Block: 893910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389302 RingCT/type: yes/0
Extra: 01d7a2e868e1fead0f8e6a8e7fb4c3d56e3a4ad6c27f40f04306dd927bbdab85b902110000000475e3f0e9000000000000000000

1 output(s) for total of 0.670046715000 dcy

stealth address amount amount idx
00: b1f3160f08e5993e42317703fef082f95838b08bf5fb84516880ff330cbc2195 0.670046715000 1350095 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": 893920, "vin": [ { "gen": { "height": 893910 } } ], "vout": [ { "amount": 670046715, "target": { "key": "b1f3160f08e5993e42317703fef082f95838b08bf5fb84516880ff330cbc2195" } } ], "extra": [ 1, 215, 162, 232, 104, 225, 254, 173, 15, 142, 106, 142, 127, 180, 195, 213, 110, 58, 74, 214, 194, 127, 64, 240, 67, 6, 221, 146, 123, 189, 171, 133, 185, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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