← previous blocknext block →recent activity
Analyzing
Block #99,854,176
18 transactions · 17 stateful · 2026-08-28 08:45:29 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,854,176 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w111w212w313w414w215w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a1642c6…5b2b
0x34b655…2a6f
10 touches
10 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd5a25205…645e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x6a1642c6c5…495b2b
Audit this contract →
← previous block·next block →recent activity