Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b9a376be1c3359bd6e9da4513dbc37eb8ad5ba6692b92ef6bdfedbdb1f0c517

Tx prefix hash: f4b7ef4ae060677377a316054da75894f3c70275810f36b51c7220a8095b6e04
Tx public key: 6c6ceb4af3ef8b6e6549c03df4cec39cf85f21cb6ed8181a211e95a3773dd2a2
Timestamp: 1648036245 Timestamp [UCT]: 2022-03-23 11:50:45 Age [y:d:h:m:s]: 03:036:10:19:46
Block: 464652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 806220 RingCT/type: yes/0
Extra: 016c6ceb4af3ef8b6e6549c03df4cec39cf85f21cb6ed8181a211e95a3773dd2a2021100000009d3fcec30000000000000000000

1 output(s) for total of 17.718024386000 dcy

stealth address amount amount idx
00: 411e0ba4caf93f104513aa445e3e7001147b58ab43a0e8553cec4e7856054830 17.718024386000 882579 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": 464662, "vin": [ { "gen": { "height": 464652 } } ], "vout": [ { "amount": 17718024386, "target": { "key": "411e0ba4caf93f104513aa445e3e7001147b58ab43a0e8553cec4e7856054830" } } ], "extra": [ 1, 108, 108, 235, 74, 243, 239, 139, 110, 101, 73, 192, 61, 244, 206, 195, 156, 248, 95, 33, 203, 110, 216, 24, 26, 33, 30, 149, 163, 119, 61, 210, 162, 2, 17, 0, 0, 0, 9, 211, 252, 236, 48, 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