← previous blocknext block →recent activity
Analyzing
Block #106,577,168
13 transactions · 12 stateful · 2026-09-20 22:01:53 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,577,168 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w18w29w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfac38cc8…fb9d
0x34b655…2a6f
6 touches
3 conflicts
0x976ee3c0…1f0f
0x34b655…2a6f
4 touches
1 conflict
0x0296a3f5…aa91
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0xa60eabc0…9f8c
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
3 conflicts on slot 0xfac38cc8b7…a4fb9d
Audit this contract →
← previous block·next block →recent activity