← previous blocknext block →recent activity

Analyzing

Block #95,373,883

29 transactions · 22 stateful · 2026-08-12 14:52:26 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.38

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,373,883  ·  29 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

0x00ddbbf2…4588

0x34b655…2a6f

6 touches
3 conflicts

0x403b061b…9f34

0x34b655…2a6f

6 touches
3 conflicts

0x53f393fa…00b9

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xf06c2cf5…61bd

0x34b655…2a6f

6 touches
3 conflicts

0xd6de93a8…9382

0x34b655…2a6f

4 touches
1 conflict

0xcd5c0ecb…4b5f

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 0x00ddbbf292…ff4588

← previous block·next block →recent activity