← previous blocknext block →recent activity
Analyzing
Block #107,444,421
25 transactions · 24 stateful · 2026-09-23 22:48:26 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,444,421 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w09w210w315w217w118w319w020w221w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x36dfe42e…23b6
0xa6afd3…d132
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0xa3d78e5e…bb33
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe9693c23…43cc
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity