← previous blocknext block →recent activity
Analyzing
Block #99,290,784
18 transactions · 18 stateful · 2026-08-26 09:16:23 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,290,784 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w38w39w411w412w513w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x823a7ba9…34c9
0x34b655…2a6f
10 touches
10 conflicts
0xf49aa5ae…67c0
0x34b655…2a6f
10 touches
10 conflicts
0xebe581d8…2696
0x34b655…2a6f
10 touches
10 conflicts
0xd9722304…6ed0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x72083f0d…082a
0x34b655…2a6f
6 touches
3 conflicts
0xd7668c61…55f8
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
10 conflicts on slot 0x823a7ba90e…d834c9
Audit this contract →
← previous block·next block →recent activity