← previous blocknext block →recent activity

Analyzing

Block #96,316,636

23 transactions · 22 stateful · 2026-08-15 21:57:23 UTC

Parallelism

70/100

Blocked

41%

Avg conflicts / tx

1.26

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,316,636  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x29c1a140…099f

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x4bd1d7fb…b907

0x34b655…2a6f

6 touches
3 conflicts

0x73670e81…2813

0x34b655…2a6f

6 touches
3 conflicts

0x7d0eaae2…60b7

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity