Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82c389d7e1319ae1f57bf368e82748ff6d10dabc39533655ccbf9a48f83a12ab

Tx prefix hash: 13f2fa98dd3cffdf3e34083e0f0a75b7d21b4fc713f965a6cec0e300f9fbdd43
Tx public key: d00acc61c54ae996a22b2353a4fbaea83319779884024aee692bee34db2641c7
Timestamp: 1723508217 Timestamp [UCT]: 2024-08-13 00:16:57 Age [y:d:h:m:s]: 00:233:18:46:25
Block: 1086637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166960 RingCT/type: yes/0
Extra: 01d00acc61c54ae996a22b2353a4fbaea83319779884024aee692bee34db2641c7021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd026e8f1ca83f76bc1fdee827ae07e0494fee46f54dd9e9ff32e0f815f2fe83 0.600000000000 1561234 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": 1086647, "vin": [ { "gen": { "height": 1086637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd026e8f1ca83f76bc1fdee827ae07e0494fee46f54dd9e9ff32e0f815f2fe83" } } ], "extra": [ 1, 208, 10, 204, 97, 197, 74, 233, 150, 162, 43, 35, 83, 164, 251, 174, 168, 51, 25, 119, 152, 132, 2, 74, 238, 105, 43, 238, 52, 219, 38, 65, 199, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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