Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d385fff652019a85e052b8e4cd7647d61eddd824ede3a0da3a45fd687b0bab5f

Tx prefix hash: 24972b4f89b569bbf3be1e1dd19400978c489cd66e62bac2b1a9e63a0c22200a
Tx public key: 6caa4ae362b4ec154fdb50b01f8c328ab5c6c9b90314abe45baa5ad150cf823f
Timestamp: 1669188464 Timestamp [UCT]: 2022-11-23 07:27:44 Age [y:d:h:m:s]: 02:161:05:12:06
Block: 637195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636959 RingCT/type: yes/0
Extra: 016caa4ae362b4ec154fdb50b01f8c328ab5c6c9b90314abe45baa5ad150cf823f021100000002faf35c9c000000000000000000

1 output(s) for total of 4.750162404000 dcy

stealth address amount amount idx
00: 3000ff0303bf3ee7644f61ed60a12cc6172d77ec81b7356453e5ca069bb2b80a 4.750162404000 1076711 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": 637205, "vin": [ { "gen": { "height": 637195 } } ], "vout": [ { "amount": 4750162404, "target": { "key": "3000ff0303bf3ee7644f61ed60a12cc6172d77ec81b7356453e5ca069bb2b80a" } } ], "extra": [ 1, 108, 170, 74, 227, 98, 180, 236, 21, 79, 219, 80, 176, 31, 140, 50, 138, 181, 198, 201, 185, 3, 20, 171, 228, 91, 170, 90, 209, 80, 207, 130, 63, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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