← previous blocknext block →recent activity
Analyzing
Block #106,191,551
22 transactions · 22 stateful · 2026-09-19 13:41:03 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,191,551 · 22 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
2w03w14w15w29w013w214w315w419w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6771eae2…7014
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x3639a9ac…3165
0x34b655…2a6f
8 touches
6 conflicts
0xb4d83521…fbc3
0x34b655…2a6f
8 touches
6 conflicts
0x315e07b8…9823
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xd597209e…9800
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 0x6771eae21e…6b7014
Audit this contract →
← previous block·next block →recent activity