← previous blocknext block →recent activity
Analyzing
Block #103,050,679
22 transactions · 17 stateful · 2026-09-08 13:25:09 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,050,679 · 22 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
2w04w05w06w18w110w013w114w215w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x25180879…8191
0x34b655…2a6f
6 touches
3 conflicts
0x55192654…91fe
0x34b655…2a6f
6 touches
3 conflicts
0x08dd17bc…799f
0x34b655…2a6f
4 touches
1 conflict
0x0eac7709…66c3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6a9e408e…3721
0x34b655…2a6f
4 touches
1 conflict
0xa016a307…63ae
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity