← previous blocknext block →recent activity
Analyzing
Block #101,322,856
24 transactions · 23 stateful · 2026-09-02 12:00:52 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,322,856 · 24 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
1w03w04w16w27w38w411w012w116w320w122w223w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb975a6c…bff4
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x5e2bd0c1…7ca2
0xa6afd3…d132
6 touches
3 conflicts
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0xebb541cb…a721
0xa6afd3…d132
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe9486384…ea03
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 0xbb975a6cb4…7fbff4
Audit this contract →
← previous block·next block →recent activity