← previous blocknext block →recent activity
Analyzing
Block #91,436,059
18 transactions · 16 stateful · 2026-07-29 20:13:56 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,436,059 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w310w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x521a91b0…b4c9
0x34b655…2a6f
6 touches
3 conflicts
0xd6195af4…534d
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x811cb01f…e507
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
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
3 conflicts on slot 0x521a91b05d…68b4c9
Audit this contract →
← previous block·next block →recent activity