Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf83e2146e341c6173c3ce8625dd0c3377d2dd7fb3c1acc715dca72d9ea02850

Tx prefix hash: 5d07f8e6e99bdf92fe31528eb4055eb038f49d24961b84d09b8de9dcc1b1b54a
Tx public key: 65825ba28b13a9e5e7bd89ecd2b05c54046a711ead05fd85e9b04a097f67dd02
Timestamp: 1577762329 Timestamp [UCT]: 2019-12-31 03:18:49 Age [y:d:h:m:s]: 05:138:17:10:32
Block: 35442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1248962 RingCT/type: yes/0
Extra: 0165825ba28b13a9e5e7bd89ecd2b05c54046a711ead05fd85e9b04a097f67dd020211000000634fb58672000000000000000000

1 output(s) for total of 468.345978682000 dcy

stealth address amount amount idx
00: c2febcdfbc2ef3cb5697d57481721a472bb764e7c0c8cd55491221f2b7ed1df0 468.345978682000 59773 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": 35452, "vin": [ { "gen": { "height": 35442 } } ], "vout": [ { "amount": 468345978682, "target": { "key": "c2febcdfbc2ef3cb5697d57481721a472bb764e7c0c8cd55491221f2b7ed1df0" } } ], "extra": [ 1, 101, 130, 91, 162, 139, 19, 169, 229, 231, 189, 137, 236, 210, 176, 92, 84, 4, 106, 113, 30, 173, 5, 253, 133, 233, 176, 74, 9, 127, 103, 221, 2, 2, 17, 0, 0, 0, 99, 79, 181, 134, 114, 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