← previous blocknext block →recent activity

Analyzing

Block #95,783,859

22 transactions · 20 stateful · 2026-08-14 01:17:07 UTC

Parallelism

59/100

Blocked

55%

Avg conflicts / tx

1.32

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #95,783,859  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x4c619b7d…f4fa

0x34b655…2a6f

6 touches
3 conflicts

0x71c72ebc…dbbb

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x83220a94…1bd7

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity