← previous blocknext block →recent activity
Analyzing
Block #101,306,826
26 transactions · 21 stateful · 2026-09-02 10:40:13 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,306,826 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w28w212w213w317w118w019w121w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x2e6427d0…c9c8
0xa6afd3…d132
4 touches
1 conflict
0x5ace3d35…9ea9
0x34b655…2a6f
4 touches
1 conflict
0x5ddc4a77…765e
0x34b655…2a6f
4 touches
1 conflict
0x6423fcab…a7c1
0x34b655…2a6f
4 touches
1 conflict
0x6bed078a…7802
0x34b655…2a6f
4 touches
1 conflict
0x7491a16e…fe54
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity