← previous blocknext block →recent activity
Analyzing
Block #91,108,987
7 transactions · 7 stateful · 2026-07-28 16:46:15 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,108,987 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc58c80b…ff79
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfd5be853…17a0
0x34b655…2a6f
4 touches
1 conflict
0xa2272beb…2baf
0x34b655…2a6f
4 touches
1 conflict
0xaebcd759…6cdc
0x34b655…2a6f
4 touches
1 conflict
0xba5ff1c3…4ff1
0x34b655…2a6f
3 touches
1 conflict
0x915c095e…c1e5
0x2b46c0…1669
2 touches
0 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
1 conflict on slot 0xcc58c80b6c…80ff79
Audit this contract →
← previous block·next block →recent activity