← previous blocknext block →recent activity
Analyzing
Block #99,606,479
17 transactions · 15 stateful · 2026-08-27 11:50:43 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,606,479 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w211w312w114w416w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc16e646d…4fb0
0x34b655…2a6f
8 touches
6 conflicts
0x70d81211…f49f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x128fb0bd…18e5
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x890b77c0…379c
0x34b655…2a6f
4 touches
1 conflict
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 0xc16e646d81…a44fb0
Audit this contract →
← previous block·next block →recent activity