← previous blocknext block →recent activity

Analyzing

Block #96,784,624

22 transactions · 21 stateful · 2026-08-17 13:11:27 UTC

Parallelism

50/100

Blocked

52%

Avg conflicts / tx

2.86

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #96,784,624  ·  22 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

0xc824469a…6425

0x34b655…2a6f

20 touches
45 conflicts

0x482471ad…122f

0x34b655…2a6f

16 touches
28 conflicts

0xe8eae8a3…bacc

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x2464f36f…724c

0x34b655…2a6f

8 touches
6 conflicts

0x4efae872…6aa8

0x34b655…2a6f

8 touches
6 conflicts

0x0a6f5e37…6c3c

0x34b655…2a6f

6 touches
3 conflicts

0x53f393fa…00b9

0x34b655…2a6f

6 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

45 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity