Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b6e74f3c509c779d91323f97f5253b00ee427e96274fe7ff15629e532f607b8

Tx prefix hash: 039878a5496b769f987db403b5bac524456cc6321645759bf0a69f7d0d929b8c
Tx public key: 8d2bc2e5a651a779626d2c126576ca1f77b89b2bcc6d0805efd5eda890114391
Timestamp: 1708904500 Timestamp [UCT]: 2024-02-25 23:41:40 Age [y:d:h:m:s]: 01:029:11:23:00
Block: 965575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282049 RingCT/type: yes/0
Extra: 018d2bc2e5a651a779626d2c126576ca1f77b89b2bcc6d0805efd5eda8901143910211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11c6054284c4f45b33ed333f18bc645e7fa20fe8bf73da5ea906dbc2299b5b03 0.600000000000 1425328 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": 965585, "vin": [ { "gen": { "height": 965575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11c6054284c4f45b33ed333f18bc645e7fa20fe8bf73da5ea906dbc2299b5b03" } } ], "extra": [ 1, 141, 43, 194, 229, 166, 81, 167, 121, 98, 109, 44, 18, 101, 118, 202, 31, 119, 184, 155, 43, 204, 109, 8, 5, 239, 213, 237, 168, 144, 17, 67, 145, 2, 17, 0, 0, 0, 6, 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