← previous blocknext block →recent activity
Analyzing
Block #106,395,592
25 transactions · 23 stateful · 2026-09-20 06:48:00 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,395,592 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w09w110w215w216w317w019w222w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x65b12d95…0991
0x34b655…2a6f
4 touches
1 conflict
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0x78cc044a…79de
0x34b655…2a6f
4 touches
1 conflict
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