← previous blocknext block →recent activity

Analyzing

Block #95,295,585

39 transactions · 30 stateful · 2026-08-12 08:15:46 UTC

Parallelism

74/100

Blocked

43%

Avg conflicts / tx

1.33

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #95,295,585  ·  39 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xc824469a…6425

0x34b655…2a6f

20 touches
45 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x0b1d86ea…d766

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x4be9812b…48a9

0x34b655…2a6f

6 touches
3 conflicts

0x7be3246e…f89f

0x34b655…2a6f

6 touches
3 conflicts

0x3df7769a…5d17

0x3bd359…433a

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

45 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity