← previous blocknext block →recent activity
Analyzing
Block #91,139,997
8 transactions · 8 stateful · 2026-07-28 19:22:14 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,139,997 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71bbf601…5874
0x34b655…2a6f
4 touches
1 conflict
0xbc66586e…20fe
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x24742942…0c3d
0x34b655…2a6f
2 touches
0 conflicts
0x2d966132…b875
0x34b655…2a6f
2 touches
0 conflicts
0x42578f4c…5779
0x34b655…2a6f
2 touches
0 conflicts
0x5060cdde…445d
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 0x71bbf601cd…6a5874
Audit this contract →
← previous block·next block →recent activity