← previous blocknext block →recent activity
Analyzing
Block #99,162,869
82 transactions · 62 stateful · 2026-08-25 22:32:46 UTC
Parallelism
81/100
Blocked
79%
Avg conflicts / tx
3.39
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #99,162,869 · 82 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w110w013w115w243w146w247w348w449w550w651w752w154w658w859w964w1065w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
32 touches
120 conflicts
0xf3d10975…0d07
0x34b655…2a6f
20 touches
45 conflicts
0xea02471d…1542
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xce567125…bb54
0xd32edf…ff58
19 touches
45 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
16 touches
28 conflicts
0x46cb45de…a568
0x188d58…ea8e
12 touches
15 conflicts
0x46cb45de…a566
0x188d58…ea8e
12 touches
15 conflicts
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: 0xf5b5f7f8…a36d70
120 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity