← previous blocknext block →recent activity

Analyzing

Block #95,424,410

20 transactions · 20 stateful · 2026-08-12 19:08:07 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,424,410  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x784eaad2…d177

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x109c2330…f629

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e65

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x734ee320…caae

0x34b655…2a6f

4 touches
1 conflict

0x784eaad2…d176

0x34b655…2a6f

4 touches
1 conflict

0x7c921df9…1fab

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x784eaad228…0ad177

← previous block·next block →recent activity