← previous blocknext block →recent activity
Analyzing
Block #101,976,163
11 transactions · 8 stateful · 2026-09-04 18:50:58 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,976,163 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8b6d32…6601
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x087e3cac…29f3
0x34b655…2a6f
2 touches
0 conflicts
0x173b64af…6c43
0x34b655…2a6f
2 touches
0 conflicts
0x1950527a…a8a6
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xcc8b6d3248…e46601
Audit this contract →
← previous block·next block →recent activity