← previous blocknext block →recent activity
Analyzing
Block #106,957,282
24 transactions · 23 stateful · 2026-09-22 05:56:04 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,957,282 · 24 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
1w02w03w19w010w111w212w313w317w418w519w020w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x858e40c0…7e30
0x34b655…2a6f
10 touches
10 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
8 touches
6 conflicts
0xfcef6587…476d
0x34b655…2a6f
6 touches
3 conflicts
0x68f6cd4d…8940
0x34b655…2a6f
6 touches
3 conflicts
0x8714eb4d…e184
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd192f4ed…d7ec
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 0x858e40c022…9e7e30
Audit this contract →
← previous block·next block →recent activity