← previous blocknext block →recent activity
Analyzing
Block #101,302,215
25 transactions · 22 stateful · 2026-09-02 10:17:00 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,302,215 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w19w210w315w318w419w020w021w123w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b267bdf…b173
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x8590b692…b267
0x34b655…2a6f
6 touches
3 conflicts
0x390e3302…49d7
0x34b655…2a6f
5 touches
3 conflicts
0x88e92ec7…696d
0x34b655…2a6f
4 touches
1 conflict
0xa7ab3866…c0c7
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 0x6b267bdfb8…87b173
Audit this contract →
← previous block·next block →recent activity