← previous blocknext block →recent activity

Analyzing

Block #95,976,755

32 transactions · 30 stateful · 2026-08-14 17:27:41 UTC

Parallelism

78/100

Blocked

40%

Avg conflicts / tx

1.03

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,976,755  ·  32 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

10 touches
10 conflicts

0xbdc80bf7…e947

0x34b655…2a6f

6 touches
3 conflicts

0x29c1a140…099f

0x34b655…2a6f

6 touches
3 conflicts

0xfbc8d004…ecc9

0x34b655…2a6f

6 touches
3 conflicts

0x53f393fa…00b9

0x34b655…2a6f

6 touches
3 conflicts

0x83f87246…1d5f

0x34b655…2a6f

4 touches
1 conflict

0x9da42530…1c86

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

10 conflicts on slot 0xec7d120df9…5d7084

← previous block·next block →recent activity