← previous blocknext block →recent activity
Analyzing
Block #99,608,031
20 transactions · 17 stateful · 2026-08-27 11:58:40 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,608,031 · 20 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
1w02w13w04w15w211w113w014w116w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbcaea56…1020
0x34b655…2a6f
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0x364d1d02…0528
0x34b655…2a6f
6 touches
3 conflicts
0xcf70e146…f042
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x5791e60d…0b7d
0x34b655…2a6f
4 touches
1 conflict
0x63016070…64d5
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 0xbbcaea56b1…921020
Audit this contract →
← previous block·next block →recent activity