← previous blocknext block →recent activity
Analyzing
Block #106,190,547
20 transactions · 18 stateful · 2026-09-19 13:36:00 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,190,547 · 20 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
1w02w13w04w15w16w211w212w313w414w315w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x684d04c0…37c4
0x34b655…2a6f
8 touches
6 conflicts
0x67a56c8b…f955
0x34b655…2a6f
8 touches
6 conflicts
0xbc417c5e…4f97
0x34b655…2a6f
8 touches
6 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0xb19f81b3…b902
0x34b655…2a6f
6 touches
3 conflicts
0xbeedaa05…9eda
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 0x684d04c07a…7b37c4
Audit this contract →
← previous block·next block →recent activity