← previous blocknext block →recent activity
Analyzing
Block #101,322,341
25 transactions · 23 stateful · 2026-09-02 11:58:16 UTC
Parallelism
84/100
Blocked
30%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,322,341 · 25 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
2w03w14w07w011w113w014w116w117w218w323w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7b5a9269…2f8a
0x34b655…2a6f
8 touches
6 conflicts
0x7151b1ad…4520
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x629e09e5…692a
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 0xc824469a90…af6426
Audit this contract →
← previous block·next block →recent activity