← previous blocknext block →recent activity
Analyzing
Block #106,434,945
31 transactions · 29 stateful · 2026-09-20 10:06:03 UTC
Parallelism
77/100
Blocked
69%
Avg conflicts / tx
1.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,434,945 · 31 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
2w03w14w15w26w07w110w116w222w223w324w425w326w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x0490581d…adaf
0x34b655…2a6f
10 touches
10 conflicts
0xc3baa205…f26e
0x34b655…2a6f
8 touches
6 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x1fa7b83d…42dd
0x34b655…2a6f
8 touches
6 conflicts
0x2836d18c…d85c
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
10 conflicts on slot 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity