← previous blocknext block →recent activity
Analyzing
Block #106,554,148
28 transactions · 24 stateful · 2026-09-20 20:06:01 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,554,148 · 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
1w02w13w14w25w08w119w220w321w424w527w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x4986f2ad…8151
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x6e4184c2…f064
0x34b655…2a6f
8 touches
6 conflicts
0x86cea35b…bdff
0x34b655…2a6f
8 touches
6 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
8 touches
6 conflicts
0xd9fdc204…0e30
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
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
6 conflicts on slot 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity