← previous blocknext block →recent activity
Analyzing
Block #106,555,208
20 transactions · 20 stateful · 2026-09-20 20:11:21 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,555,208 · 20 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
1w02w13w04w15w16w212w213w314w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc53799eb…d928
0x34b655…2a6f
8 touches
6 conflicts
0x04994ed2…9032
0x34b655…2a6f
8 touches
6 conflicts
0x1715a62a…7b93
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x7462b8f2…6312
0x34b655…2a6f
8 touches
6 conflicts
0x8f5a38d8…c230
0x34b655…2a6f
8 touches
6 conflicts
0xa56b5f6e…e64a
0x34b655…2a6f
8 touches
6 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 0xc53799ebcf…a9d928
Audit this contract →
← previous block·next block →recent activity