← previous blocknext block →recent activity

Analyzing

Block #95,549,024

16 transactions · 13 stateful · 2026-08-13 05:34:55 UTC

Parallelism

69/100

Blocked

62%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,549,024  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x2840c278…bbc7

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0xf6deafb5…5c25

0x34b655…2a6f

4 touches
1 conflict

0x0a0cecef…4ed0

0x34b655…2a6f

4 touches
1 conflict

0x28ceceef…ecc2

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xac3bc39a…72e0

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

3 conflicts on slot 0x2840c278a3…01bbc7

← previous block·next block →recent activity