← previous blocknext block →recent activity
Analyzing
Block #106,362,709
25 transactions · 23 stateful · 2026-09-20 04:02:30 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,362,709 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w110w214w315w116w417w518w619w721w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaccf4b21…e0ce
0x34b655…2a6f
16 touches
28 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x8d175439…fb79
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x2130a548…c1de
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
28 conflicts on slot 0xaccf4b214f…c2e0ce
Audit this contract →
← previous block·next block →recent activity