← previous blocknext block →recent activity
Analyzing
Block #106,282,275
26 transactions · 19 stateful · 2026-09-19 21:17:44 UTC
Parallelism
81/100
Blocked
58%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,282,275 · 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
3w04w15w06w27w011w112w213w215w319w320w321w122w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xddd20e39…d524
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5f13dc38…5584
0x34b655…2a6f
6 touches
3 conflicts
0xd8a7deb7…f22a
0xd32edf…ff58
5 touches
3 conflicts
0x4fb5185c…f2b3
0x065c9d…c394
5 touches
3 conflicts
0x366a19b0…f065
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
10 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity