← previous blocknext block →recent activity
Analyzing
Block #106,425,293
17 transactions · 16 stateful · 2026-09-20 09:17:28 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,425,293 · 17 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
1w02w13w04w15w16w210w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bcfe5f…6c71
0x34b655…2a6f
8 touches
6 conflicts
0x6ab5ad08…9c6d
0x34b655…2a6f
8 touches
6 conflicts
0x857e8166…5ba6
0x34b655…2a6f
8 touches
6 conflicts
0xd7668c61…55f8
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xe9457301…83cd
0x34b655…2a6f
6 touches
3 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
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 0x38bcfe5f82…986c71
Audit this contract →
← previous block·next block →recent activity