← previous blocknext block →recent activity

Analyzing

Block #95,746,956

24 transactions · 22 stateful · 2026-08-13 22:11:31 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.58

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,746,956  ·  24 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xeae24c…0be0

6 touches
3 conflicts

0x966e45cf…0f25

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xacd1b162…bee6

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xe8eae8a3…bacc

0x34b655…2a6f

4 touches
1 conflict

0x53e50026…6d8c

0x2b46c0…1669

2 touches
0 conflicts

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 0xca841faae5…71486a

← previous block·next block →recent activity