← previous blocknext block →recent activity

Analyzing

Block #95,985,019

17 transactions · 16 stateful · 2026-08-14 18:09:15 UTC

Parallelism

53/100

Blocked

56%

Avg conflicts / tx

1.47

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,985,019  ·  17 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

0xe42b6c1e…e069

0x34b655…2a6f

10 touches
10 conflicts

0x5906754f…b584

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0x35a9f06c…7689

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…641f

0x34b655…2a6f

8 touches
6 conflicts

0x9cf9008a…d826

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

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

10 conflicts on slot 0xe42b6c1e88…46e069

← previous block·next block →recent activity