← previous blocknext block →recent activity

Analyzing

Block #95,076,047

17 transactions · 16 stateful · 2026-08-11 13:42:18 UTC

Parallelism

65/100

Blocked

56%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,076,047  ·  17 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

0x25205c26…56c9

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xf0d45ffd…89cf

0x34b655…2a6f

6 touches
3 conflicts

0x30ae635d…5e67

0x34b655…2a6f

6 touches
3 conflicts

0x3e412550…5c60

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0d488000…3831

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 0x25205c2640…8e56c9

← previous block·next block →recent activity