← previous blocknext block →recent activity
Analyzing
Block #106,457,376
22 transactions · 19 stateful · 2026-09-20 11:59:00 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,457,376 · 22 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
1w02w13w14w05w211w013w315w417w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0de7749d…5bef
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
8 touches
6 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
8 touches
6 conflicts
0x357e744f…e15b
0x34b655…2a6f
8 touches
6 conflicts
0x375df097…cfd4
0x34b655…2a6f
8 touches
6 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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 0x0de7749d55…5c5bef
Audit this contract →
← previous block·next block →recent activity