← previous blocknext block →recent activity
Analyzing
Block #94,681,613
22 transactions · 22 stateful · 2026-08-10 04:36:03 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,681,613 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w07w18w09w212w114w319w120w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xecb4264b…7cf9
0x34b655…2a6f
6 touches
3 conflicts
0x539ac47f…eb6f
0x34b655…2a6f
6 touches
3 conflicts
0xa1fb92e0…d478
0x34b655…2a6f
6 touches
3 conflicts
0x6f9752ff…3ec8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity