← previous blocknext block →recent activity
Analyzing
Block #99,504,599
24 transactions · 24 stateful · 2026-08-27 03:12:53 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
2.08
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,504,599 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w110w211w314w415w516w617w718w119w720w823w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b4edd58…9623
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd814f518…f5b4
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
6 touches
3 conflicts
0x5d8975d1…341a
0x34b655…2a6f
6 touches
3 conflicts
0x64275949…d698
0x34b655…2a6f
6 touches
3 conflicts
0x6771eae2…7014
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: Perpl
28 conflicts on slot 0x6b4edd5859…d59623
Audit this contract →
← previous block·next block →recent activity