← previous blocknext block →recent activity
Analyzing
Block #99,449,056
8 transactions · 7 stateful · 2026-08-26 22:33:13 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,449,056 · 8 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
2w03w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b5f2081…f3c5
0x34b655…2a6f
6 touches
3 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
6 touches
3 conflicts
0x16d77246…bac5
0x34b655…2a6f
4 touches
1 conflict
0x1ada3764…d906
0x34b655…2a6f
4 touches
1 conflict
0x1faeed20…190f
0x34b655…2a6f
4 touches
1 conflict
0x280aaa58…1c52
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x5969523e…5191
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 0x4b5f208101…60f3c5
Audit this contract →
← previous block·next block →recent activity