← previous blocknext block →recent activity
Analyzing
Block #106,576,172
14 transactions · 13 stateful · 2026-09-20 21:56:52 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,576,172 · 14 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
2w03w19w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdad20621…06b1
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x886db264…846e
0x34b655…2a6f
6 touches
3 conflicts
0x5f72d58f…c445
0x34b655…2a6f
6 touches
3 conflicts
0x99def33c…aff3
0x34b655…2a6f
6 touches
3 conflicts
0x7e59f6d5…68f0
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 0xdad20621a2…0306b1
Audit this contract →
← previous block·next block →recent activity