Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc43fc237054cc7b83fa46328f18de0765744570286882d85b7effb423964009

Tx prefix hash: 6a7d4d567ea6fd73903cde2736c0b74eb157b0d0188cfa07e0d602050c0e0b9f
Tx public key: 6831534f034bc31e48dec6a52d000f72b519d3af11b4567ab7aac08f85d84326
Timestamp: 1713753046 Timestamp [UCT]: 2024-04-22 02:30:46 Age [y:d:h:m:s]: 00:203:03:07:24
Block: 1005758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145412 RingCT/type: yes/0
Extra: 016831534f034bc31e48dec6a52d000f72b519d3af11b4567ab7aac08f85d843260211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95c8f1cff3f39018af882d9a9f012455519995cddf3d77a2c3a398769222c913 0.600000000000 1466554 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": 1005768, "vin": [ { "gen": { "height": 1005758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95c8f1cff3f39018af882d9a9f012455519995cddf3d77a2c3a398769222c913" } } ], "extra": [ 1, 104, 49, 83, 79, 3, 75, 195, 30, 72, 222, 198, 165, 45, 0, 15, 114, 181, 25, 211, 175, 17, 180, 86, 122, 183, 170, 192, 143, 133, 216, 67, 38, 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