← previous blocknext block →recent activity
Analyzing
Block #106,199,393
24 transactions · 23 stateful · 2026-09-19 14:20:31 UTC
Parallelism
71/100
Blocked
70%
Avg conflicts / tx
1.54
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,199,393 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w27w38w110w213w416w117w518w621w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8dc6c70d…37a6
0x34b655…2a6f
12 touches
15 conflicts
0xa5555ca8…4b01
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
8 touches
6 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
15 conflicts on slot 0x8dc6c70d97…ce37a6
Audit this contract →
← previous block·next block →recent activity