← previous blocknext block →recent activity

Analyzing

Block #95,349,448

24 transactions · 23 stateful · 2026-08-12 12:48:36 UTC

Parallelism

67/100

Blocked

48%

Avg conflicts / tx

0.96

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,349,448  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x52b477bc…7ccf

0x34b655…2a6f

8 touches
6 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x95c47f03…f1bb

0x34b655…2a6f

6 touches
3 conflicts

0xd30f9e74…d404

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x38bdc5d3…a632

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

6 conflicts on slot 0x52b477bcb8…5d7ccf

← previous block·next block →recent activity