← previous blocknext block →recent activity

Analyzing

Block #99,318,256

19 transactions · 18 stateful · 2026-08-26 11:34:34 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,318,256  ·  19 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xa93fb268…e452

0x34b655…2a6f

6 touches
3 conflicts

0x2130a548…c1de

0x34b655…2a6f

6 touches
3 conflicts

0x93767c37…35f6

0x34b655…2a6f

6 touches
3 conflicts

0x42e5184f…4e8b

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…1266

0x34b655…2a6f

4 touches
1 conflict

0x664144de…d0a2

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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

3 conflicts on slot 0xa93fb26858…2ae452

← previous block·next block →recent activity