← previous blocknext block →recent activity

Analyzing

Block #96,318,479

24 transactions · 24 stateful · 2026-08-15 22:06:39 UTC

Parallelism

58/100

Blocked

63%

Avg conflicts / tx

1.5

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #96,318,479  ·  24 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xb3fb9fb5…64db

0x34b655…2a6f

10 touches
10 conflicts

0x4cabb80a…46bf

0x34b655…2a6f

10 touches
10 conflicts

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0x5d2c01c7…439f

0x34b655…2a6f

4 touches
1 conflict

0x6a4868a5…367e

0x34b655…2a6f

4 touches
1 conflict

0x839be85f…a40b

0x34b655…2a6f

4 touches
1 conflict

0x8dfb88f5…5592

0x34b655…2a6f

4 touches
1 conflict

0xc782ec05…5bb2

0xa6afd3…d132

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 0xb3fb9fb561…7664db

← previous block·next block →recent activity