← previous blocknext block →recent activity
Analyzing
Block #106,376,961
24 transactions · 22 stateful · 2026-09-20 05:14:14 UTC
Parallelism
75/100
Blocked
64%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,376,961 · 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
1w02w14w05w16w09w210w311w212w113w414w316w417w419w522w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x973f9be7…4f61
0x34b655…2a6f
8 touches
6 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0x4118bd12…924a
0x34b655…2a6f
6 touches
3 conflicts
0x4681609f…6493
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
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
6 conflicts on slot 0x973f9be73c…2e4f61
Audit this contract →
← previous block·next block →recent activity