← previous blocknext block →recent activity
Analyzing
Block #101,302,470
21 transactions · 17 stateful · 2026-09-02 10:18:17 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,302,470 · 21 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
2w04w06w17w214w015w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0x902578eb…33f2
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xec1d6663…6042
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x46279ae7…20dd
0x34ae4d…3fc5
2 touches
0 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
2 touches
0 conflicts
0x6eff310a…c34c
0x34ae4d…3fc5
2 touches
0 conflicts
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
1 conflict on slot 0x6771eae21e…6b7014
Audit this contract →
← previous block·next block →recent activity