← previous blocknext block →recent activity
Analyzing
Block #106,464,067
15 transactions · 13 stateful · 2026-09-20 12:32:40 UTC
Parallelism
60/100
Blocked
54%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,464,067 · 15 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
1w02w05w06w18w19w210w311w412w514w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1927b58…f161
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0x40c5b3ec…f478
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0x67c6f44a…f21c
0x34b655…2a6f
4 touches
1 conflict
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 0xb1927b5859…36f161
Audit this contract →
← previous block·next block →recent activity