← previous blocknext block →recent activity
Analyzing
Block #101,321,775
20 transactions · 17 stateful · 2026-09-02 11:55:25 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,321,775 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w09w111w215w316w417w018w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x615bc8cc…15d2
0x34b655…2a6f
6 touches
3 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x816924c8…bac9
0x34b655…2a6f
4 touches
1 conflict
0x9c4e75f7…96c8
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 0x615bc8cc79…5215d2
Audit this contract →
← previous block·next block →recent activity