← previous blocknext block →recent activity
Analyzing
Block #99,356,294
30 transactions · 24 stateful · 2026-08-26 14:46:00 UTC
Parallelism
83/100
Blocked
54%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,356,294 · 30 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
2w04w15w06w17w19w010w111w216w218w220w322w426w127w228w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e3e9f18…f684
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
6 touches
3 conflicts
0xdeeebbbe…ab9d
0xd32edf…ff58
5 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0x6e3e9f18fd…eff684
Audit this contract →
← previous block·next block →recent activity