← previous blocknext block →recent activity
Analyzing
Block #99,884,229
63 transactions · 63 stateful · 2026-08-28 11:17:02 UTC
Parallelism
94/100
Blocked
11%
Avg conflicts / tx
0.16
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,884,229 · 63 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
3w04w15w28w312w214w057w158w059w162w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x9aa7036b…a2a7
0xa6afd3…d132
4 touches
1 conflict
0xadce6355…03bf
0xa6afd3…d132
4 touches
1 conflict
0x247cfb80…cca8
0x34b655…2a6f
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0x49b0842d…0a93
0x34b655…2a6f
2 touches
0 conflicts
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