← previous blocknext block →recent activity
Analyzing
Block #91,557,802
9 transactions · 8 stateful · 2026-07-30 06:26:26 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,557,802 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a89094e…f5b2
0x34b655…2a6f
4 touches
1 conflict
0xcf061e9a…ff21
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5a8d5be5…d9a4
0x34b655…2a6f
4 touches
1 conflict
0x2e546dd9…4c50
0x34b655…2a6f
4 touches
1 conflict
0x6eb3e5af…064e
0x34b655…2a6f
4 touches
1 conflict
0x830ecda3…b1b8
0x34b655…2a6f
4 touches
1 conflict
0x4e50038e…6e29
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
1 conflict on slot 0x9a89094e2b…f6f5b2
Audit this contract →
← previous block·next block →recent activity