← previous blocknext block →recent activity
Analyzing
Block #91,445,924
10 transactions · 9 stateful · 2026-07-29 21:03:33 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
0.8
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,445,924 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w16w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0x442e26a3…e968
0x34b655…2a6f
6 touches
3 conflicts
0x50c388ce…aee7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xe64d2555…8caf
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 0xef5959a35a…d32a2f
Audit this contract →
← previous block·next block →recent activity