← previous blocknext block →recent activity
Analyzing
Block #101,067,869
10 transactions · 9 stateful · 2026-09-01 14:37:55 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,067,869 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x12f81d84…c430
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x423af0c6…8145
0x34b655…2a6f
4 touches
1 conflict
0x510dd776…2f09
0x34b655…2a6f
3 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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity