← previous blocknext block →recent activity
Analyzing
Block #99,484,365
59 transactions · 53 stateful · 2026-08-27 01:31:02 UTC
Parallelism
92/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,484,365 · 59 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
10w011w112w214w315w016w017w153w457w058w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf692017e…686e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x09e0690d…6e3d
0xe52b14…7230
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 0xf692017e1c…cd686e
Audit this contract →
← previous block·next block →recent activity