Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3350ab6e52250e533a82ca3e517e08161c3505bf344327ccbc0fca45bbbe03ff

Tx prefix hash: bf9c28ea1d7d07ea377ddf8b481c1caffb6ea0409d322a347e48bd36ec413f18
Tx public key: d505c35912e710fa71e5a79dbf2083c1f97357a513e3af271eac82ae55f2ee73
Timestamp: 1645241378 Timestamp [UCT]: 2022-02-19 03:29:38 Age [y:d:h:m:s]: 03:264:09:14:59
Block: 441641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 966732 RingCT/type: yes/0
Extra: 01d505c35912e710fa71e5a79dbf2083c1f97357a513e3af271eac82ae55f2ee73021100000002c9067537000000000000000000

1 output(s) for total of 21.118366574000 dcy

stealth address amount amount idx
00: aa5d33a8730bddbe429493dc904bc69193475bbf0b3a39705a3c7af572283d74 21.118366574000 854246 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": 441651, "vin": [ { "gen": { "height": 441641 } } ], "vout": [ { "amount": 21118366574, "target": { "key": "aa5d33a8730bddbe429493dc904bc69193475bbf0b3a39705a3c7af572283d74" } } ], "extra": [ 1, 213, 5, 195, 89, 18, 231, 16, 250, 113, 229, 167, 157, 191, 32, 131, 193, 249, 115, 87, 165, 19, 227, 175, 39, 30, 172, 130, 174, 85, 242, 238, 115, 2, 17, 0, 0, 0, 2, 201, 6, 117, 55, 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