← previous blocknext block →recent activity
Analyzing
Block #99,866,572
17 transactions · 17 stateful · 2026-08-28 09:48:06 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,866,572 · 17 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
4w06w17w28w39w310w411w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16993363…919c
0x34b655…2a6f
10 touches
10 conflicts
0xb856d1a1…1f18
0x34b655…2a6f
8 touches
6 conflicts
0x54986533…78b2
0x34b655…2a6f
8 touches
6 conflicts
0xebe581d8…2696
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0x35b0198e…3e0d
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
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
10 conflicts on slot 0x1699336379…ec919c
Audit this contract →
← previous block·next block →recent activity