← previous blocknext block →recent activity
Analyzing
Block #91,078,315
25 transactions · 23 stateful · 2026-07-28 14:11:54 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,078,315 · 25 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
1w02w04w15w06w19w010w111w214w015w116w218w119w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x92115abd…ad76
0x34b655…2a6f
6 touches
3 conflicts
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x37bef14c…a6d5
0x34b655…2a6f
4 touches
1 conflict
0x4ec5ff53…d470
0x34b655…2a6f
4 touches
1 conflict
0x59cd6c8f…4e99
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x90a66fa7…9014
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity