← previous blocknext block →recent activity
Analyzing
Block #106,570,253
16 transactions · 15 stateful · 2026-09-20 21:27:04 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,570,253 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f00a5b3…bf76
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x29c7f30c…f1dd
0x34b655…2a6f
2 touches
0 conflicts
0x400ae040…e5de
0x34b655…2a6f
2 touches
0 conflicts
0x826cce18…251c
0x34b655…2a6f
2 touches
0 conflicts
0x2b36ecc6…093e
0x3c2269…cf62
2 touches
0 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
1 conflict on slot 0x1f00a5b37a…aebf76
Audit this contract →
← previous block·next block →recent activity