← previous blocknext block →recent activity
Analyzing
Block #99,357,215
18 transactions · 17 stateful · 2026-08-26 14:50:38 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,357,215 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w28w39w111w213w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29cd05f5…390c
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x17ff2059…ddb4
0x34b655…2a6f
4 touches
1 conflict
0x9b76a37f…58c3
0x34b655…2a6f
4 touches
1 conflict
0x13807d54…85db
0x34b655…2a6f
2 touches
0 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 0x29cd05f5e7…a9390c
Audit this contract →
← previous block·next block →recent activity