← previous blocknext block →recent activity
Analyzing
Block #99,988,061
15 transactions · 13 stateful · 2026-08-28 20:00:16 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,988,061 · 15 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
3w05w06w17w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da59c2b…d7b2
0x34b655…2a6f
6 touches
3 conflicts
0x7662d077…c6bc
0x34b655…2a6f
6 touches
3 conflicts
0x42e917f7…ed8c
0x34b655…2a6f
4 touches
1 conflict
0x8be49d52…7fb4
0x34b655…2a6f
4 touches
1 conflict
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x27bb8a53…2fd9
0x34b655…2a6f
3 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 0x5da59c2b2f…b6d7b2
Audit this contract →
← previous block·next block →recent activity