← previous blocknext block →recent activity
Analyzing
Block #91,203,395
10 transactions · 10 stateful · 2026-07-29 00:41:09 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,203,395 · 10 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0xd52424b6…774c
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x032128e1…4edf
0x34b655…2a6f
2 touches
0 conflicts
0x03d53e11…3f6f
0x34b655…2a6f
2 touches
0 conflicts
0x03fd9ae9…211d
0x34b655…2a6f
2 touches
0 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
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 0x6b267bdfb8…87b173
Audit this contract →
← previous block·next block →recent activity