Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d77b99e7571f4813b90b68a0eccf97c87803e692205515398d99501cd7c1a334

Tx prefix hash: e6474322b9d8c979df0473e024144e67032644fba9bab6ff52383503cf9d65fb
Tx public key: 058cecd607596ac1db21aaf8cc159cb98f5e2ae5b4968b0375e5618d4bf23af2
Timestamp: 1592761408 Timestamp [UCT]: 2020-06-21 17:43:28 Age [y:d:h:m:s]: 05:132:18:57:35
Block: 110225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1291710 RingCT/type: yes/0
Extra: 01058cecd607596ac1db21aaf8cc159cb98f5e2ae5b4968b0375e5618d4bf23af202110000003f46a11e8a000000000000000000

1 output(s) for total of 264.715618652000 dcy

stealth address amount amount idx
00: c1c5c086563e643eb69eded7f0e3ed74c63338e1e54679fb9cb14cf52d324584 264.715618652000 190863 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": 110235, "vin": [ { "gen": { "height": 110225 } } ], "vout": [ { "amount": 264715618652, "target": { "key": "c1c5c086563e643eb69eded7f0e3ed74c63338e1e54679fb9cb14cf52d324584" } } ], "extra": [ 1, 5, 140, 236, 214, 7, 89, 106, 193, 219, 33, 170, 248, 204, 21, 156, 185, 143, 94, 42, 229, 180, 150, 139, 3, 117, 229, 97, 141, 75, 242, 58, 242, 2, 17, 0, 0, 0, 63, 70, 161, 30, 138, 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