← previous blocknext block →recent activity
Analyzing
Block #91,905,751
35 transactions · 30 stateful · 2026-07-31 11:36:52 UTC
Parallelism
86/100
Blocked
43%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,905,751 · 35 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w112w013w117w018w120w221w222w225w326w327w428w431w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef79589c…0088
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
8 touches
6 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xef79589c5b…f20088
Audit this contract →
← previous block·next block →recent activity