Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 801edf3aea5c0b598057608951d5912d0a59c34f906665844e57d94acd533f7c

Tx prefix hash: 6c53f06d2b39891171dda4b2e7bb16a8ed6e80386aed47be14d3791a2e2dc776
Tx public key: feea1e70426873f144aede8304827a12cde90a17be3f57d6a4404abe48b2bd68
Timestamp: 1731325248 Timestamp [UCT]: 2024-11-11 11:40:48 Age [y:d:h:m:s]: 01:000:07:00:50
Block: 1151359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258625 RingCT/type: yes/0
Extra: 01feea1e70426873f144aede8304827a12cde90a17be3f57d6a4404abe48b2bd680211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65d4d1b8a2811c7b39c43ebdac48bc766889e9dce2c6fda2668673c30d9c348f 0.600000000000 1636876 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": 1151369, "vin": [ { "gen": { "height": 1151359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65d4d1b8a2811c7b39c43ebdac48bc766889e9dce2c6fda2668673c30d9c348f" } } ], "extra": [ 1, 254, 234, 30, 112, 66, 104, 115, 241, 68, 174, 222, 131, 4, 130, 122, 18, 205, 233, 10, 23, 190, 63, 87, 214, 164, 64, 74, 190, 72, 178, 189, 104, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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