← previous blocknext block →recent activity

Analyzing

Block #95,594,394

19 transactions · 17 stateful · 2026-08-13 09:23:06 UTC

Parallelism

68/100

Blocked

53%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,594,394  ·  19 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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x86977b3d…a9c4

0x34b655…2a6f

6 touches
3 conflicts

0x835907de…69f9

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf40e9839…0001

0x34b655…2a6f

5 touches
3 conflicts

0x0f2d78b1…7363

0x34b655…2a6f

4 touches
1 conflict

0xe9452241…95a3

0x34b655…2a6f

4 touches
1 conflict

0x947bb79d…6458

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

← previous block·next block →recent activity