← previous blocknext block →recent activity

Analyzing

Block #95,915,930

26 transactions · 24 stateful · 2026-08-14 12:21:41 UTC

Parallelism

58/100

Blocked

58%

Avg conflicts / tx

1.88

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #95,915,930  ·  26 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x53f393fa…00b9

0x34b655…2a6f

16 touches
28 conflicts

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xc38eef52…c98c

0x34b655…2a6f

6 touches
3 conflicts

0xf8c9546a…ebba

0x34b655…2a6f

6 touches
3 conflicts

0x2d94ecd9…43db

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

28 conflicts on slot 0x53f393fafd…2a00b9

← previous block·next block →recent activity