← previous blocknext block →recent activity
Analyzing
Block #99,257,786
14 transactions · 13 stateful · 2026-08-26 06:30:19 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,257,786 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w09w110w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4984f7be…d515
0x34b655…2a6f
6 touches
3 conflicts
0xa2ed4d66…74ea
0x34b655…2a6f
6 touches
3 conflicts
0xb7b8aab2…fbf2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x42e5184f…4e8b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
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
3 conflicts on slot 0x4984f7bedd…bfd515
Audit this contract →
← previous block·next block →recent activity