← previous blocknext block →recent activity
Analyzing
Block #99,619,162
23 transactions · 21 stateful · 2026-08-27 12:55:58 UTC
Parallelism
87/100
Blocked
48%
Avg conflicts / tx
0.74
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,619,162 · 23 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
1w02w13w04w16w07w08w112w113w014w215w116w217w221w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb856d1a1…1f18
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xfc5d79bb…362c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x5b09bf44…5907
0xa6afd3…d132
6 touches
3 conflicts
0xefc629e7…776d
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
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
3 conflicts on slot 0xb856d1a127…bf1f18
Audit this contract →
← previous block·next block →recent activity