← previous blocknext block →recent activity
Analyzing
Block #106,546,393
28 transactions · 25 stateful · 2026-09-20 19:27:00 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,546,393 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w29w010w114w315w418w020w421w522w124w026w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x3643741b…109c
0x34b655…2a6f
6 touches
3 conflicts
0x366a19b0…f065
0x34b655…2a6f
6 touches
3 conflicts
0x46fb9ba7…9dd0
0x34b655…2a6f
6 touches
3 conflicts
0x5a541bec…80fc
0x34b655…2a6f
6 touches
3 conflicts
0x829f4217…bd38
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
10 conflicts on slot 0xddd20e3989…a2d524
Audit this contract →
← previous block·next block →recent activity