← previous blocknext block →recent activity

Analyzing

Block #95,596,391

22 transactions · 19 stateful · 2026-08-13 09:33:09 UTC

Parallelism

68/100

Blocked

53%

Avg conflicts / tx

1.41

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,596,391  ·  22 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

0x734ee320…caae

0x34b655…2a6f

14 touches
21 conflicts

0xec7d120d…7084

0x34b655…2a6f

8 touches
6 conflicts

0x08636046…e60f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x5edb8bbe…bc75

0x34b655…2a6f

4 touches
1 conflict

0x4deeee1b…8c0c

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x77ab3b32…6ce4

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

21 conflicts on slot 0x734ee32053…cecaae

← previous block·next block →recent activity