← previous blocknext block →recent activity
Analyzing
Block #106,424,181
30 transactions · 26 stateful · 2026-09-20 09:11:52 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,424,181 · 30 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
1w02w13w04w15w16w28w09w110w216w017w121w122w223w324w425w527w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3684e08…c96a
0x34b655…2a6f
8 touches
6 conflicts
0x422bab7d…0f6c
0x34b655…2a6f
8 touches
6 conflicts
0x4102cb2a…3b17
0x34b655…2a6f
8 touches
6 conflicts
0xd1ed6c82…869d
0x34b655…2a6f
8 touches
6 conflicts
0x6d955786…1327
0x34b655…2a6f
8 touches
6 conflicts
0x4cbfdd01…4d18
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xfc24540b…6463
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 0xe3684e088a…5fc96a
Audit this contract →
← previous block·next block →recent activity