← previous blocknext block →recent activity
Analyzing
Block #91,297,029
12 transactions · 9 stateful · 2026-07-29 08:33:05 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,297,029 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b26b03e…ecb6
0x34b655…2a6f
6 touches
3 conflicts
0x87a24499…0acf
0x34b655…2a6f
6 touches
3 conflicts
0x62386583…1aa0
0x34b655…2a6f
6 touches
3 conflicts
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x20cb8909…c6c3
0x34b655…2a6f
4 touches
1 conflict
0x8f63f383…6eda
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xab975ec4…daaa
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 0x0b26b03e28…35ecb6
Audit this contract →
← previous block·next block →recent activity