← previous blocknext block →recent activity
Analyzing
Block #106,576,018
19 transactions · 17 stateful · 2026-09-20 21:56:05 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.84
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,576,018 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w19w210w312w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b6e959d…158f
0x34b655…2a6f
8 touches
6 conflicts
0x9b96d962…259e
0x34b655…2a6f
8 touches
6 conflicts
0x94e7f277…471b
0x34b655…2a6f
8 touches
6 conflicts
0xe77107b6…426b
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x588380ee…0a5c
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
6 conflicts on slot 0x3b6e959d6b…f8158f
Audit this contract →
← previous block·next block →recent activity