← previous blocknext block →recent activity
Analyzing
Block #99,472,376
22 transactions · 20 stateful · 2026-08-27 00:30:37 UTC
Parallelism
82/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,472,376 · 22 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
1w02w13w24w05w06w111w012w113w214w319w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf83843c9…706a
0xe52b14…7230
8 touches
6 conflicts
0xf83843c9…7068
0xe52b14…7230
8 touches
6 conflicts
0x1f18f001…2c08
0xe52b14…7230
8 touches
6 conflicts
0x6b1f8e83…1c81
0xe52b14…7230
8 touches
6 conflicts
0xf3ab898f…a814
0xe52b14…7230
8 touches
6 conflicts
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 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: 0xe52b1424…bb7230
6 conflicts on slot 0xf83843c9b9…a5706a
Audit this contract →
← previous block·next block →recent activity