← previous blocknext block →recent activity
Analyzing
Block #91,291,654
21 transactions · 20 stateful · 2026-07-29 08:06:02 UTC
Parallelism
76/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,291,654 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w212w313w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc014bcf3…3ac7
0x34b655…2a6f
8 touches
6 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x34dff15c…05a9
0x34b655…2a6f
4 touches
1 conflict
0x3b4d4025…3960
0x34b655…2a6f
4 touches
1 conflict
0x50260e8c…4789
0x34b655…2a6f
4 touches
1 conflict
0x69c131ce…d733
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
6 conflicts on slot 0xc014bcf38f…c73ac7
Audit this contract →
← previous block·next block →recent activity