← previous blocknext block →recent activity
Analyzing
Block #96,600,407
22 transactions · 22 stateful · 2026-08-16 21:44:55 UTC
Parallelism
68/100
Blocked
64%
Avg conflicts / tx
2.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,600,407 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w18w29w210w311w113w314w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x56153262…21ce
0x34b655…2a6f
12 touches
15 conflicts
0x31616f97…1acc
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xf55013f2…fe73
0x34b655…2a6f
10 touches
10 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
8 touches
6 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
8 touches
6 conflicts
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: Perpl
15 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity