← previous blocknext block →recent activity
Analyzing
Block #106,922,203
19 transactions · 18 stateful · 2026-09-22 02:59:29 UTC
Parallelism
58/100
Blocked
61%
Avg conflicts / tx
1.89
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,922,203 · 19 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
1w02w13w24w07w18w29w010w111w312w414w515w216w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f4ef2db…f1b2
0x34b655…2a6f
16 touches
28 conflicts
0x206f4379…e08a
0x34b655…2a6f
8 touches
6 conflicts
0x9f46242e…f550
0x34b655…2a6f
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x485d2778…aa5f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00bd8926…a214
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 0x2f4ef2dbe9…e7f1b2
Audit this contract →
← previous block·next block →recent activity