← previous blocknext block →recent activity
Analyzing
Block #99,659,046
22 transactions · 19 stateful · 2026-08-27 16:17:30 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,659,046 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w110w011w114w315w417w119w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50807b43…b4ee
0x34b655…2a6f
8 touches
6 conflicts
0xe226a0be…c046
0x34b655…2a6f
8 touches
6 conflicts
0x4a45b318…9716
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x0004b1fc…36b1
0x34b655…2a6f
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x50807b43d0…68b4ee
Audit this contract →
← previous block·next block →recent activity