← previous blocknext block →recent activity
Analyzing
Block #99,960,435
24 transactions · 24 stateful · 2026-08-28 17:41:05 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,960,435 · 24 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
1w02w15w06w17w08w111w213w114w115w216w217w320w421w523w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d5c5d72…914b
0x34b655…2a6f
10 touches
10 conflicts
0x53f7214d…8ec6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x24bb46f7…3853
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5d116df7…de83
0x34b655…2a6f
4 touches
1 conflict
0x63dd87d0…212a
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
10 conflicts on slot 0x6d5c5d726f…33914b
Audit this contract →
← previous block·next block →recent activity