← previous blocknext block →recent activity
Analyzing
Block #99,868,725
19 transactions · 13 stateful · 2026-08-28 09:58:56 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,868,725 · 19 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
7w09w110w211w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23c1dd54…8fdf
0x34b655…2a6f
8 touches
6 conflicts
0xb856d1a1…1f18
0x34b655…2a6f
8 touches
6 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
8 touches
6 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0x1408a100…f721
0x34b655…2a6f
6 touches
3 conflicts
0x5c12ac0e…fb32
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xf13772ac…4c17
0x34b655…2a6f
5 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 0x23c1dd540a…688fdf
Audit this contract →
← previous block·next block →recent activity