← previous blocknext block →recent activity

Analyzing

Block #95,656,358

28 transactions · 25 stateful · 2026-08-13 14:34:48 UTC

Parallelism

79/100

Blocked

32%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,656,358  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb39cb1d8…effa

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xd4543ca3…19a8

0x34b655…2a6f

6 touches
3 conflicts

0x07d8b1e8…78c6

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x585cacce…5bdc

0x34b655…2a6f

4 touches
1 conflict

0x71ba83aa…be81

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

15 conflicts on slot 0xb39cb1d8c6…28effa

← previous block·next block →recent activity