← previous blocknext block →recent activity

Analyzing

Block #95,745,084

23 transactions · 18 stateful · 2026-08-13 22:02:06 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,745,084  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x1e2bd3ed…19a2

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xc6b1d981…1be2

0xa6afd3…d132

4 touches
1 conflict

0x68c0df95…6eae

0x065c9d…c394

4 touches
1 conflict

0xd85af236…5e8b

0x40c49f…2af0

4 touches
1 conflict

0x7e0b7922…c351

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

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 0x1e2bd3ed9d…4719a2

← previous block·next block →recent activity