← previous blocknext block →recent activity

Analyzing

Block #95,555,943

22 transactions · 20 stateful · 2026-08-13 06:09:43 UTC

Parallelism

73/100

Blocked

35%

Avg conflicts / tx

0.64

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,555,943  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x66d5e476…8a1f

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe20cfb89…cd07

0x754704…b603

4 touches
1 conflict

0x43fd3667…094b

0x34b655…2a6f

4 touches
1 conflict

0x4f858307…7642

0x34b655…2a6f

4 touches
1 conflict

0x5475cd67…5763

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x85e18a5f…8a88

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

6 conflicts on slot 0x66d5e476c0…268a1f

← previous block·next block →recent activity