← previous blocknext block →recent activity
Analyzing
Block #99,331,878
14 transactions · 13 stateful · 2026-08-26 12:43:05 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,331,878 · 14 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
1w03w04w15w26w37w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x032995c2…a5be
0xd32edf…ff58
5 touches
3 conflicts
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x62462b9e…bbd6
0x34b655…2a6f
4 touches
1 conflict
0x6efd1872…7582
0x34b655…2a6f
4 touches
1 conflict
0x8b5365d3…442d
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0x9f63b181…919d
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity