Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dab126352711e4c7b2b9f1c866964f89ecd46b3f24db710ca41af9a32c56eac

Tx prefix hash: 62098a2b5925fba1187d7b7d78a36f843d15449744b006a57df4b46681772067
Tx public key: 69bf0992d066a7042960dbac338b0a5e86d492b0eb932a3ad316f781e1c87200
Timestamp: 1698912503 Timestamp [UCT]: 2023-11-02 08:08:23 Age [y:d:h:m:s]: 01:158:15:00:02
Block: 882936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374358 RingCT/type: yes/0
Extra: 0169bf0992d066a7042960dbac338b0a5e86d492b0eb932a3ad316f781e1c872000211000000014b8f5122000000000000000000

1 output(s) for total of 0.728562001000 dcy

stealth address amount amount idx
00: 363abebf8dfd52e2495f51b2e5f3fc34b7db8e7471561ebc740cc035357493ec 0.728562001000 1338618 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": 882946, "vin": [ { "gen": { "height": 882936 } } ], "vout": [ { "amount": 728562001, "target": { "key": "363abebf8dfd52e2495f51b2e5f3fc34b7db8e7471561ebc740cc035357493ec" } } ], "extra": [ 1, 105, 191, 9, 146, 208, 102, 167, 4, 41, 96, 219, 172, 51, 139, 10, 94, 134, 212, 146, 176, 235, 147, 42, 58, 211, 22, 247, 129, 225, 200, 114, 0, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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