← previous blocknext block →recent activity
Analyzing
Block #88,354,111
31 transactions · 24 stateful · 2026-07-17 13:25:04 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,354,111 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w09w114w015w116w219w020w022w123w224w125w226w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x756913cf…e7bd
0xa6afd3…d132
6 touches
3 conflicts
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xdaf5ed0d…16af
0x34b655…2a6f
4 touches
1 conflict
0xe4a8aa45…da90
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: Perpl
6 conflicts on slot 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity