Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ce6bb3e13955efb9e91be99d8e7c46fd775f37b061e2ca2b2c729eb3a2463e7

Tx prefix hash: b887ebaf49d7e0d0bf7136111cd25306e66b2db7c1a131cd92a1c8651fe69265
Tx public key: 6e8af10c581af46ec556fd1332804c6893e8f0c7ef9cf9f77b612576557113f4
Timestamp: 1705336355 Timestamp [UCT]: 2024-01-15 16:32:35 Age [y:d:h:m:s]: 01:300:18:28:36
Block: 935972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473781 RingCT/type: yes/0
Extra: 016e8af10c581af46ec556fd1332804c6893e8f0c7ef9cf9f77b612576557113f40211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e35701784e67cff16ca6f0a0f4595a1bef98ca960c9acf5adcef51d075c40f9f 0.600000000000 1393994 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": 935982, "vin": [ { "gen": { "height": 935972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e35701784e67cff16ca6f0a0f4595a1bef98ca960c9acf5adcef51d075c40f9f" } } ], "extra": [ 1, 110, 138, 241, 12, 88, 26, 244, 110, 197, 86, 253, 19, 50, 128, 76, 104, 147, 232, 240, 199, 239, 156, 249, 247, 123, 97, 37, 118, 85, 113, 19, 244, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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