← previous blocknext block →recent activity

Analyzing

Block #95,406,424

23 transactions · 22 stateful · 2026-08-12 17:37:08 UTC

Parallelism

70/100

Blocked

55%

Avg conflicts / tx

1.39

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,406,424  ·  23 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

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0xfb9f51f4…0f16

0x34b655…2a6f

6 touches
3 conflicts

0x4783345c…4a90

0x34b655…2a6f

4 touches
1 conflict

0x563bbb55…861a

0x34b655…2a6f

4 touches
1 conflict

0x58d0a23c…5d3a

0x34b655…2a6f

4 touches
1 conflict

0x5edb8bbe…bc75

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