← previous blocknext block →recent activity

Analyzing

Block #99,119,628

26 transactions · 23 stateful · 2026-08-25 18:55:14 UTC

Parallelism

73/100

Blocked

35%

Avg conflicts / tx

0.54

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,119,628  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbb97db90…4c93

0xc8689a…ee79

4 touches
1 conflict

0x9b2d3bee…8eec

0x34b655…2a6f

4 touches
1 conflict

0x9c2fc330…0091

0x34b655…2a6f

4 touches
1 conflict

0x9f76ca95…8215

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x42041fec…bd86

0x754704…b603

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 0x482471adbb…39122f

← previous block·next block →recent activity