← previous blocknext block →recent activity

Analyzing

Block #95,708,280

20 transactions · 19 stateful · 2026-08-13 18:56:42 UTC

Parallelism

75/100

Blocked

37%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,708,280  ·  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

0x588380ee…0a5c

0x34b655…2a6f

6 touches
3 conflicts

0xafb8e71e…9285

0x34b655…2a6f

6 touches
3 conflicts

0xb2fa1675…4e07

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x6f900be0…cd6e

0x34b655…2a6f

4 touches
1 conflict

0x957c875f…b3f9

0x34b655…2a6f

4 touches
1 conflict

0xa494952f…d178

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0x588380ee30…d00a5c

← previous block·next block →recent activity