← previous blocknext block →recent activity
Analyzing
Block #106,393,184
21 transactions · 19 stateful · 2026-09-20 06:35:53 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,393,184 · 21 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
1w02w13w04w15w28w29w315w016w117w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0262e1c6…52e1
0x34b655…2a6f
10 touches
10 conflicts
0xde00fca6…3969
0x34b655…2a6f
8 touches
6 conflicts
0x29d45f2d…6576
0x34b655…2a6f
8 touches
6 conflicts
0x31d88d27…7617
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x065a3bb1…e176
0x34b655…2a6f
6 touches
3 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
10 conflicts on slot 0x0262e1c696…e752e1
Audit this contract →
← previous block·next block →recent activity