← previous blocknext block →recent activity
Analyzing
Block #91,546,417
8 transactions · 7 stateful · 2026-07-30 05:29:10 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,546,417 · 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd58b9a66…1c23
0x34b655…2a6f
4 touches
1 conflict
0xfc7739ba…284a
0x34b655…2a6f
4 touches
1 conflict
0x76c49694…51b3
0x34b655…2a6f
4 touches
1 conflict
0xd01910c9…9418
0x34b655…2a6f
4 touches
1 conflict
0x2f475d04…03fa
0x34b655…2a6f
2 touches
0 conflicts
0x42d5e8f3…5930
0x34b655…2a6f
2 touches
0 conflicts
0x42d5e8f3…5931
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity