← previous blocknext block →recent activity

Analyzing

Block #96,640,065

23 transactions · 20 stateful · 2026-08-17 01:04:22 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.35

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #96,640,065  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

10 touches
10 conflicts

0x38c6ff01…689f

0x34b655…2a6f

6 touches
3 conflicts

0x8d3529f1…3732

0x34b655…2a6f

6 touches
3 conflicts

0xe5eb3c33…0e3a

0x34b655…2a6f

6 touches
3 conflicts

0xea1b8c07…b969

0x34b655…2a6f

6 touches
3 conflicts

0xaf5e9c44…e3fe

0x34b655…2a6f

5 touches
3 conflicts

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

15 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity