← previous blocknext block →recent activity
Analyzing
Block #99,194,571
34 transactions · 28 stateful · 2026-08-26 01:12:16 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
1.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,194,571 · 34 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w09w010w111w112w213w318w219w420w524w631w733w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xb1856468…e84f
0x34b655…2a6f
8 touches
6 conflicts
0x9a100e05…c541
0x34b655…2a6f
8 touches
6 conflicts
0x631b4113…baa9
0x34b655…2a6f
8 touches
6 conflicts
0x7ea1cfdf…81c0
0xa6afd3…d132
6 touches
3 conflicts
0x718531a4…47d6
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity