← previous blocknext block →recent activity
Analyzing
Block #93,419,081
24 transactions · 22 stateful · 2026-08-05 18:30:47 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,419,081 · 24 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
1w04w05w19w210w311w012w113w316w118w419w221w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cc65720…396c
0x34b655…2a6f
6 touches
3 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
6 touches
3 conflicts
0xcc351d6d…256b
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x428b6e5b…8909
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x6d010e51…b2f0
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
3 conflicts on slot 0x0cc657206f…8a396c
Audit this contract →
← previous block·next block →recent activity