← previous blocknext block →recent activity
Analyzing
Block #106,554,541
36 transactions · 23 stateful · 2026-09-20 20:08:00 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,554,541 · 36 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
2w08w09w110w218w119w328w429w031w132w133w234w535w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x1e63ce19…13c8
0x34b655…2a6f
6 touches
3 conflicts
0x21d22421…0b7a
0x34b655…2a6f
6 touches
3 conflicts
0x3643741b…109c
0x34b655…2a6f
6 touches
3 conflicts
0x366a19b0…f065
0x34b655…2a6f
6 touches
3 conflicts
0x5a541bec…80fc
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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