← previous blocknext block →recent activity
Analyzing
Block #101,956,735
13 transactions · 12 stateful · 2026-09-04 17:12:31 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,956,735 · 13 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
4w05w17w29w010w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x637a4c28…2510
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd1e92f08…d3ba
0x34b655…2a6f
4 touches
1 conflict
0xdc7b9eda…e616
0x34b655…2a6f
4 touches
1 conflict
0xec2a8d79…70cb
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x0fb354ca…3ad7
0x34b655…2a6f
4 touches
1 conflict
0x305cebcc…8317
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 0x637a4c2803…4d2510
Audit this contract →
← previous block·next block →recent activity