← previous blocknext block →recent activity
Analyzing
Block #91,018,862
9 transactions · 8 stateful · 2026-07-28 09:12:43 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,018,862 · 9 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
0xc22a0c80…6c90
0x34b655…2a6f
4 touches
1 conflict
0x1ea2b1f6…1d57
0x34b655…2a6f
4 touches
1 conflict
0x1ea2b1f6…1d58
0x34b655…2a6f
4 touches
1 conflict
0x2e095751…39dc
0x34b655…2a6f
4 touches
1 conflict
0x361f4a1b…1f14
0x34b655…2a6f
4 touches
1 conflict
0x3d968bdd…0f95
0x34b655…2a6f
3 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x53e50026…6d8c
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 0xc22a0c8052…406c90
Audit this contract →
← previous block·next block →recent activity