← previous blocknext block →recent activity
Analyzing
Block #91,209,061
29 transactions · 25 stateful · 2026-07-29 01:09:39 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
0.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,209,061 · 29 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w08w19w213w214w115w216w317w418w522w323w426w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd22dd5e8…83ff
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x5c568791…31a8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd957c18f…5cfc
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
6 touches
3 conflicts
0xefcdf197…96a2
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 0xd22dd5e874…5383ff
Audit this contract →
← previous block·next block →recent activity