← previous blocknext block →recent activity
Analyzing
Block #101,308,675
22 transactions · 18 stateful · 2026-09-02 10:49:31 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,308,675 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w18w29w310w411w513w620w721w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x5ce19b50…f20f
0x34b655…2a6f
6 touches
3 conflicts
0x21ab438a…93dd
0x34b655…2a6f
6 touches
3 conflicts
0x178a61ad…4958
0x34b655…2a6f
4 touches
1 conflict
0x49339736…b223
0x34b655…2a6f
4 touches
1 conflict
0x4ae38164…15f0
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5482e6e6…09d0
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity