← previous blocknext block →recent activity

Analyzing

Block #96,220,094

19 transactions · 17 stateful · 2026-08-15 13:51:48 UTC

Parallelism

53/100

Blocked

76%

Avg conflicts / tx

1.95

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #96,220,094  ·  19 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x9a3463f0…0b73

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x2ad2e6d1…e192

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x3cf50d44…961b

0x34b655…2a6f

8 touches
6 conflicts

0x3f5b9011…1bae

0x34b655…2a6f

8 touches
6 conflicts

0x8a4ec63f…41c5

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0x9a3463f0c8…ca0b73

← previous block·next block →recent activity