← previous blocknext block →recent activity
Analyzing
Block #93,342,983
9 transactions · 9 stateful · 2026-08-05 12:08:10 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,342,983 · 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf5e16e2…f2a7
0x34b655…2a6f
4 touches
1 conflict
0xa8488658…af8b
0x34b655…2a6f
4 touches
1 conflict
0x021afc04…da69
0x34b655…2a6f
2 touches
0 conflicts
0x021afc04…da6a
0x34b655…2a6f
2 touches
0 conflicts
0x12028e5c…112a
0x34b655…2a6f
2 touches
0 conflicts
0x34b2aef8…79e3
0x34b655…2a6f
2 touches
0 conflicts
0x46db48f8…9bff
0x34b655…2a6f
2 touches
0 conflicts
0x66bdb4c2…7ea6
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 0xcf5e16e288…9ef2a7
Audit this contract →
← previous block·next block →recent activity