← previous blocknext block →recent activity
Analyzing
Block #91,404,868
13 transactions · 12 stateful · 2026-07-29 17:35:52 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,404,868 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
4 touches
1 conflict
0x1526b11f…8b21
0x34b655…2a6f
4 touches
1 conflict
0xd39c85ba…d77a
0x34b655…2a6f
4 touches
1 conflict
0x24beab0f…ee70
0x34b655…2a6f
2 touches
0 conflicts
0x24e3bf88…17bf
0x34b655…2a6f
2 touches
0 conflicts
0x2f91ff6a…6111
0x34b655…2a6f
2 touches
0 conflicts
0x5f60967a…8c2d
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity