← previous blocknext block →recent activity
Analyzing
Block #106,198,246
30 transactions · 28 stateful · 2026-09-19 14:14:45 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,198,246 · 30 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
1w02w13w04w15w16w28w09w116w017w018w119w120w022w023w124w225w326w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0x8f5a38d8…c230
0x34b655…2a6f
8 touches
6 conflicts
0xa6cfac02…c8c8
0x34b655…2a6f
8 touches
6 conflicts
0xd597209e…9800
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 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity