← previous blocknext block →recent activity
Analyzing
Block #91,961,312
20 transactions · 19 stateful · 2026-07-31 16:16:21 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,961,312 · 20 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
1w07w19w213w314w415w516w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xab5ba139…ea6f
0x34b655…2a6f
6 touches
3 conflicts
0x319a6895…8b88
0x34b655…2a6f
4 touches
1 conflict
0x539ac47f…eb6f
0x34b655…2a6f
4 touches
1 conflict
0x67a9f76d…0b84
0x34b655…2a6f
4 touches
1 conflict
0x67a9f76d…0b85
0x34b655…2a6f
4 touches
1 conflict
0x6eb3e5af…064e
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity