← previous blocknext block →recent activity

Analyzing

Block #95,075,759

25 transactions · 23 stateful · 2026-08-11 13:40:51 UTC

Parallelism

72/100

Blocked

52%

Avg conflicts / tx

1.44

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,075,759  ·  25 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

0x734ee320…caae

0x34b655…2a6f

12 touches
15 conflicts

0x8eef368f…aa21

0x34b655…2a6f

8 touches
6 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xfc8cd993…5c11

0x34b655…2a6f

6 touches
3 conflicts

0x52f3d91c…1822

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641e

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 0x734ee32053…cecaae

← previous block·next block →recent activity