← previous blocknext block →recent activity
Analyzing
Block #107,823,135
18 transactions · 12 stateful · 2026-09-25 06:36:40 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,823,135 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a20ad66…fc63
0x34b655…2a6f
10 touches
10 conflicts
0x66fc0764…05fd
0x34b655…2a6f
10 touches
10 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 touches
3 conflicts
0x90a021f0…f922
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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
10 conflicts on slot 0x6a20ad6681…eafc63
Audit this contract →
← previous block·next block →recent activity