Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33a8ce06779b36d7d9f6f317ff610f844e8e000add41c989af2d5f58e1905494

Tx prefix hash: 0797ae0ac6410329f39c7791e9b40d51fd6a377c95ae16daa887a11f5a097ee8
Tx public key: 3ee028235c031624e637bf3ca9da96f1cda5dd18150f787c3c9c8c669887b96e
Timestamp: 1635598252 Timestamp [UCT]: 2021-10-30 12:50:52 Age [y:d:h:m:s]: 04:002:07:01:18
Block: 363637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1038509 RingCT/type: yes/0
Extra: 013ee028235c031624e637bf3ca9da96f1cda5dd18150f787c3c9c8c669887b96e0211000000064a0f5013000000000000000000

1 output(s) for total of 38.293059779000 dcy

stealth address amount amount idx
00: 09f659576beff4d51961c0bcab0ac593d3d82f0e21b7ac228964226f7fc36d56 38.293059779000 739011 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": 363647, "vin": [ { "gen": { "height": 363637 } } ], "vout": [ { "amount": 38293059779, "target": { "key": "09f659576beff4d51961c0bcab0ac593d3d82f0e21b7ac228964226f7fc36d56" } } ], "extra": [ 1, 62, 224, 40, 35, 92, 3, 22, 36, 230, 55, 191, 60, 169, 218, 150, 241, 205, 165, 221, 24, 21, 15, 120, 124, 60, 156, 140, 102, 152, 135, 185, 110, 2, 17, 0, 0, 0, 6, 74, 15, 80, 19, 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