← previous blocknext block →recent activity
Analyzing
Block #89,855,814
33 transactions · 32 stateful · 2026-07-24 07:20:36 UTC
Parallelism
58/100
Blocked
69%
Avg conflicts / tx
3.39
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #89,855,814 · 33 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w16w27w313w014w015w116w117w218w219w320w321w422w423w524w525w626w727w828w929w1030w1131w1232w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
28 touches
91 conflicts
0x92339d95…0800
0xb1c8ea…8888
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc6cece75…ea3a
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x0000a8fd…758888
91 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity