← previous blocknext block →recent activity
Analyzing
Block #106,931,970
18 transactions · 18 stateful · 2026-09-22 03:48:39 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,931,970 · 18 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
1w02w13w25w07w08w19w210w311w112w213w314w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04994ed2…9032
0x34b655…2a6f
10 touches
10 conflicts
0x743f0e02…73ec
0x34b655…2a6f
8 touches
6 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x69168e33…6e1f
0x34b655…2a6f
8 touches
6 conflicts
0x3a82529f…f8ba
0x34b655…2a6f
6 touches
3 conflicts
0x858e40c0…7e30
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
10 conflicts on slot 0x04994ed232…129032
Audit this contract →
← previous block·next block →recent activity