Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86ee88e309f0e9e858f18b84800116319b0d9b91484222134335368b1d816985

Tx prefix hash: f416316dfefd9c4a0e163fd129f55b9bbdb5cf5c140d198b989084e986cae7c5
Tx public key: 3cee9e980229c568ade9f371b2dc04fb67017e4da9359dfec72bcaa672b6aa4d
Timestamp: 1698242094 Timestamp [UCT]: 2023-10-25 13:54:54 Age [y:d:h:m:s]: 01:089:16:52:41
Block: 877389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325289 RingCT/type: yes/0
Extra: 013cee9e980229c568ade9f371b2dc04fb67017e4da9359dfec72bcaa672b6aa4d0211000000054b8f5122000000000000000000

1 output(s) for total of 0.760056781000 dcy

stealth address amount amount idx
00: 45b73f533f6cb674739c32ada0ccd614b0bf68d31b3ac0533300e0f1ff8f2395 0.760056781000 1332763 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": 877399, "vin": [ { "gen": { "height": 877389 } } ], "vout": [ { "amount": 760056781, "target": { "key": "45b73f533f6cb674739c32ada0ccd614b0bf68d31b3ac0533300e0f1ff8f2395" } } ], "extra": [ 1, 60, 238, 158, 152, 2, 41, 197, 104, 173, 233, 243, 113, 178, 220, 4, 251, 103, 1, 126, 77, 169, 53, 157, 254, 199, 43, 202, 166, 114, 182, 170, 77, 2, 17, 0, 0, 0, 5, 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