← previous blocknext block →recent activity
Analyzing
Block #106,480,708
24 transactions · 21 stateful · 2026-09-20 13:56:24 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,480,708 · 24 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
2w012w013w115w217w318w319w420w521w623w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1af52201…398e
0x34b655…2a6f
12 touches
15 conflicts
0xc8cb0701…3926
0x34b655…2a6f
10 touches
10 conflicts
0xa3169b10…f337
0x34b655…2a6f
10 touches
10 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0x22323081…0d0a
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0x5655f5c3…6b75
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
15 conflicts on slot 0x1af5220140…eb398e
Audit this contract →
← previous block·next block →recent activity