Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b780ea851a0289752d84f58ce23bd46e395e02e31d76fbfc95ad5c7557dae359

Tx prefix hash: f5bdcc63d45b814c967ff0d7eb6c667632197f0aec3e4c8fadbfca9d5ace5d56
Tx public key: 85fce5ea2eb7c638b5ef23663bfd52472fe736d2e3bacca1a2f0ffda99269220
Timestamp: 1706850783 Timestamp [UCT]: 2024-02-02 05:13:03 Age [y:d:h:m:s]: 01:073:13:22:17
Block: 948535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313635 RingCT/type: yes/0
Extra: 0185fce5ea2eb7c638b5ef23663bfd52472fe736d2e3bacca1a2f0ffda992692200211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b87c9e63fc9ded7325a83043bf626a1ce6c132af3f750789f530c21cac1ffd2 0.600000000000 1406963 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": 948545, "vin": [ { "gen": { "height": 948535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b87c9e63fc9ded7325a83043bf626a1ce6c132af3f750789f530c21cac1ffd2" } } ], "extra": [ 1, 133, 252, 229, 234, 46, 183, 198, 56, 181, 239, 35, 102, 59, 253, 82, 71, 47, 231, 54, 210, 227, 186, 204, 161, 162, 240, 255, 218, 153, 38, 146, 32, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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