← previous blocknext block →recent activity
Analyzing
Block #91,417,845
24 transactions · 18 stateful · 2026-07-29 18:41:25 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,417,845 · 24 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
3w05w19w010w111w214w016w317w420w421w522w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1ec7ada6…505b
0x34b655…2a6f
4 touches
1 conflict
0x3483ef58…0874
0x34b655…2a6f
4 touches
1 conflict
0x552908a1…e44f
0x34b655…2a6f
4 touches
1 conflict
0x5e4a27a0…ffce
0x34b655…2a6f
4 touches
1 conflict
0x6a10a152…a08f
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