Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2babba944cbc53e13c4601de47e8089a746d9b7801c1174c5c931fa006801bd

Tx prefix hash: 92a7d23cd2582cf3f622aec66e34dbc83328b40f241e569bcf73c42f67753a85
Tx public key: 23237d1bab83f7283ac0ab9a19b8c70e3c0e1b9aad9fa82382c2d3db3c669b7d
Timestamp: 1712647712 Timestamp [UCT]: 2024-04-09 07:28:32 Age [y:d:h:m:s]: 00:322:16:53:32
Block: 996569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230717 RingCT/type: yes/0
Extra: 0123237d1bab83f7283ac0ab9a19b8c70e3c0e1b9aad9fa82382c2d3db3c669b7d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e84211225818024015acc65b59e9544612a71a7c38f40d5e16162460038a8535 0.600000000000 1456991 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": 996579, "vin": [ { "gen": { "height": 996569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e84211225818024015acc65b59e9544612a71a7c38f40d5e16162460038a8535" } } ], "extra": [ 1, 35, 35, 125, 27, 171, 131, 247, 40, 58, 192, 171, 154, 25, 184, 199, 14, 60, 14, 27, 154, 173, 159, 168, 35, 130, 194, 211, 219, 60, 102, 155, 125, 2, 17, 0, 0, 0, 4, 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