← previous blocknext block →recent activity
Analyzing
Block #106,100,457
28 transactions · 27 stateful · 2026-09-19 06:02:37 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,100,457 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w29w210w213w314w416w517w622w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731d145d…380b
0x34b655…2a6f
12 touches
15 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8590b692…b267
0x34b655…2a6f
6 touches
3 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0xfd1a5849…13e1
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
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
15 conflicts on slot 0x731d145d00…3f380b
Audit this contract →
← previous block·next block →recent activity