← previous blocknext block →recent activity
Analyzing
Block #91,549,317
8 transactions · 7 stateful · 2026-07-30 05:43:45 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,549,317 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7accd167…4103
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2dc
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xbc4e7b49…3d2d
0x34b655…2a6f
4 touches
1 conflict
0xc57b566d…8591
0x34b655…2a6f
4 touches
1 conflict
0xfb874a6c…caa0
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
1 conflict on slot 0x7accd16767…934103
Audit this contract →
← previous block·next block →recent activity