← previous blocknext block →recent activity
Analyzing
Block #106,934,073
22 transactions · 20 stateful · 2026-09-22 03:59:14 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,934,073 · 22 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
3w05w18w09w110w211w312w413w514w618w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7aa9720…56df
0x34b655…2a6f
14 touches
21 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf823984e…87b2
0x34b655…2a6f
4 touches
1 conflict
0x34c48330…703f
0x34b655…2a6f
4 touches
1 conflict
0x1f396cee…862f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
21 conflicts on slot 0xb7aa972000…2456df
Audit this contract →
← previous block·next block →recent activity