← previous blocknext block →recent activity

Analyzing

Block #99,155,814

16 transactions · 15 stateful · 2026-08-25 21:57:17 UTC

Parallelism

69/100

Blocked

47%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,155,814  ·  16 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

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x9ae56910…fe50

0x34b655…2a6f

6 touches
3 conflicts

0x705ab4ae…0162

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x1f396cee…862f

0x34b655…2a6f

4 touches
1 conflict

0x4cff6b80…47a8

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 0xbde524f475…b143bf

← previous block·next block →recent activity