← previous blocknext block →recent activity
Analyzing
Block #106,389,549
34 transactions · 24 stateful · 2026-09-20 06:17:35 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,389,549 · 34 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
5w09w010w111w012w116w218w320w426w328w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc8cb0701…3926
0x34b655…2a6f
10 touches
10 conflicts
0x2be916fc…a6da
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7cbbdd3f…65b0
0x34b655…2a6f
4 touches
1 conflict
0x8c92c3c9…e85b
0x34b655…2a6f
4 touches
1 conflict
0xa3169b10…f337
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity