Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03300375ca5ca1c1dac65c93c6ce448e5988c462e5766437560dbae6c1a40abc

Tx prefix hash: dd87dc0bebe71c9a17be39e2d5be51a71556141df53c5c0ea6eebe5f23293179
Tx public key: d040c18c25ca6daedb051cc0a63fa2fde593f5e5cb3269d9a4c1e466ff97b19a
Timestamp: 1613571049 Timestamp [UCT]: 2021-02-17 14:10:49 Age [y:d:h:m:s]: 03:322:12:18:58
Block: 200839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 989604 RingCT/type: yes/0
Extra: 01d040c18c25ca6daedb051cc0a63fa2fde593f5e5cb3269d9a4c1e466ff97b19a021100000022a45716b1000000000000000000

1 output(s) for total of 132.600494289000 dcy

stealth address amount amount idx
00: cb097d93109de860187b3a4a9969d3c5433e34e51b0c7b081cd0e8c9cff08c0e 132.600494289000 411051 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": 200849, "vin": [ { "gen": { "height": 200839 } } ], "vout": [ { "amount": 132600494289, "target": { "key": "cb097d93109de860187b3a4a9969d3c5433e34e51b0c7b081cd0e8c9cff08c0e" } } ], "extra": [ 1, 208, 64, 193, 140, 37, 202, 109, 174, 219, 5, 28, 192, 166, 63, 162, 253, 229, 147, 245, 229, 203, 50, 105, 217, 164, 193, 228, 102, 255, 151, 177, 154, 2, 17, 0, 0, 0, 34, 164, 87, 22, 177, 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