← previous blocknext block →recent activity
Analyzing
Block #100,791,522
23 transactions · 20 stateful · 2026-08-31 15:27:17 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,791,522 · 23 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
1w02w03w15w07w110w011w113w115w216w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdc9915b5…542c
0x34b655…2a6f
6 touches
3 conflicts
0xd2dfd9bc…3eec
0x34b655…2a6f
6 touches
3 conflicts
0x6f5f06af…a612
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x7cdf3968…b396
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a1
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity