← previous blocknext block →recent activity

Analyzing

Block #95,593,024

18 transactions · 15 stateful · 2026-08-13 09:16:13 UTC

Parallelism

61/100

Blocked

60%

Avg conflicts / tx

1.06

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,593,024  ·  18 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

0xafb8e71e…9285

0x34b655…2a6f

8 touches
6 conflicts

0x424934c8…f2f1

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x757b0543…e087

0x34b655…2a6f

4 touches
1 conflict

0x8e9077d3…a150

0x34b655…2a6f

4 touches
1 conflict

0x966e45cf…0f25

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 0xafb8e71eb0…ec9285

← previous block·next block →recent activity