← previous blocknext block →recent activity
Analyzing
Block #99,504,587
25 transactions · 22 stateful · 2026-08-27 03:12:49 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,504,587 · 25 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
1w02w13w05w16w07w08w110w212w313w016w317w418w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ec34d4f…5fa1
0x34b655…2a6f
8 touches
6 conflicts
0x91cdfdeb…7feb
0x34b655…2a6f
6 touches
3 conflicts
0x4387ba94…e195
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xdc6a8e4b…d6f8
0x34b655…2a6f
6 touches
3 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x6c0e32fc…a6ca
0x34b655…2a6f
4 touches
1 conflict
0x72747dd3…0afc
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 0x0ec34d4fb7…105fa1
Audit this contract →
← previous block·next block →recent activity