← previous blocknext block →recent activity
Analyzing
Block #107,651,387
12 transactions · 11 stateful · 2026-09-24 16:10:53 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,651,387 · 12 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
4w06w18w09w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf91c851e…8617
0x34b655…2a6f
4 touches
1 conflict
0xac808a27…82db
0x34b655…2a6f
4 touches
1 conflict
0x25144f94…1854
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaae6463e…bfcc
0x34b655…2a6f
4 touches
1 conflict
0x941bd594…21fd
0x34b655…2a6f
2 touches
0 conflicts
0x95a02492…1bed
0x34b655…2a6f
2 touches
0 conflicts
0xa3ed5a09…c6d3
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 0xf91c851e28…f58617
Audit this contract →
← previous block·next block →recent activity