← previous blocknext block →recent activity
Analyzing
Block #106,372,407
24 transactions · 21 stateful · 2026-09-20 04:51:18 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,372,407 · 24 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
1w03w04w15w06w18w012w214w315w416w117w218w519w420w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5c478d0…2409
0x34b655…2a6f
12 touches
15 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
10 touches
10 conflicts
0x0f270a31…640c
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x4681609f…6493
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 0xe5c478d0c4…292409
Audit this contract →
← previous block·next block →recent activity