← previous blocknext block →recent activity

Analyzing

Block #96,590,284

21 transactions · 21 stateful · 2026-08-16 20:54:00 UTC

Parallelism

67/100

Blocked

48%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,590,284  ·  21 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

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x745952b2…d90c

0x34b655…2a6f

8 touches
6 conflicts

0xb5f244d5…f550

0x34b655…2a6f

8 touches
6 conflicts

0x971de9f2…68b3

0x34b655…2a6f

8 touches
6 conflicts

0x9cf9008a…d826

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

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

10 conflicts on slot 0xd66696e0dc…230842

← previous block·next block →recent activity