Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f778df857bc59ff4dea6ebe7c1c11be7c896b896d90614322fe7785a31293f1c

Tx prefix hash: 9d8986eea746614bd1888e1de107d754bd0935b67d68e141089be019e2d08101
Tx public key: 9ce4866ad272ad19f1501dba0a57c59c39dd1a998b4e19da416b94c31d4eb2e8
Timestamp: 1698480983 Timestamp [UCT]: 2023-10-28 08:16:23 Age [y:d:h:m:s]: 01:191:10:40:16
Block: 879377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397830 RingCT/type: yes/0
Extra: 019ce4866ad272ad19f1501dba0a57c59c39dd1a998b4e19da416b94c31d4eb2e80211000000034b8f5122000000000000000000

1 output(s) for total of 0.748615760000 dcy

stealth address amount amount idx
00: b8a0d16bbd933bdd38489a01f61673a131b02f0d21a7b5661ef76e71146d7800 0.748615760000 1334887 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": 879387, "vin": [ { "gen": { "height": 879377 } } ], "vout": [ { "amount": 748615760, "target": { "key": "b8a0d16bbd933bdd38489a01f61673a131b02f0d21a7b5661ef76e71146d7800" } } ], "extra": [ 1, 156, 228, 134, 106, 210, 114, 173, 25, 241, 80, 29, 186, 10, 87, 197, 156, 57, 221, 26, 153, 139, 78, 25, 218, 65, 107, 148, 195, 29, 78, 178, 232, 2, 17, 0, 0, 0, 3, 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