← previous blocknext block →recent activity
Analyzing
Block #106,772,160
26 transactions · 23 stateful · 2026-09-21 14:24:13 UTC
Parallelism
81/100
Blocked
26%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,772,160 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w115w018w019w120w221w322w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf1bbd371…e541
0x34b655…2a6f
8 touches
6 conflicts
0xe141f2b8…f446
0x34b655…2a6f
6 touches
3 conflicts
0xf4b664ae…f2b9
0x34b655…2a6f
6 touches
3 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
6 touches
3 conflicts
0x59b1a0b3…75ba
0x34b655…2a6f
6 touches
3 conflicts
0x0a6f5e37…6c3c
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
6 conflicts on slot 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity