← previous blocknext block →recent activity
Analyzing
Block #99,991,588
17 transactions · 16 stateful · 2026-08-28 20:18:02 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,991,588 · 17 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
3w05w06w07w18w212w013w114w215w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5222901c…d3d2
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x87384755…461f
0xd32edf…ff58
5 touches
3 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0x6c28863e…840e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641d
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 0x5222901c84…f1d3d2
Audit this contract →
← previous block·next block →recent activity