← previous blocknext block →recent activity
Analyzing
Block #99,618,825
20 transactions · 19 stateful · 2026-08-27 12:54:15 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,618,825 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w17w08w19w010w111w212w113w214w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
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