← previous blocknext block →recent activity
Analyzing
Block #106,577,604
21 transactions · 21 stateful · 2026-09-20 22:04:04 UTC
Parallelism
76/100
Blocked
71%
Avg conflicts / tx
1.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,577,604 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w17w08w19w210w311w312w413w314w415w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x159cff26…7665
0x34b655…2a6f
8 touches
6 conflicts
0x4089d428…b018
0x34b655…2a6f
8 touches
6 conflicts
0xbc61e883…c859
0x34b655…2a6f
8 touches
6 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4ee0b65a…6d40
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 0x159cff262c…e57665
Audit this contract →
← previous block·next block →recent activity