← previous blocknext block →recent activity
Analyzing
Block #101,816,962
25 transactions · 23 stateful · 2026-09-04 05:26:38 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.52
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,816,962 · 25 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
1w02w13w04w29w011w014w015w118w019w120w221w122w223w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f7214d…8ec6
0x34b655…2a6f
6 touches
3 conflicts
0x997ccc40…4dfd
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0003
0xf5b5f7…6d70
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x50951f37…219c
0x3bd359…433a
6 touches
3 conflicts
0x947bb79d…6458
0x34b655…2a6f
4 touches
1 conflict
0xcc973852…d99a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x53f7214d0d…cc8ec6
Audit this contract →
← previous block·next block →recent activity