← previous blocknext block →recent activity

Analyzing

Block #95,637,255

18 transactions · 15 stateful · 2026-08-13 12:58:42 UTC

Parallelism

89/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #95,637,255  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xa940f3a4…c5e7

0x34b655…2a6f

4 touches
1 conflict

0xa940f3a4…c5e8

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xb6ba6de1…ffd7

0x34b655…2a6f

4 touches
1 conflict

0x0b1a9431…183e

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

1 conflict on slot 0x737acb7813…fafce8

← previous block·next block →recent activity