← previous blocknext block →recent activity

Analyzing

Block #94,794,513

25 transactions · 23 stateful · 2026-08-10 14:05:23 UTC

Parallelism

72/100

Blocked

52%

Avg conflicts / tx

1.32

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,794,513  ·  25 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

0x2840c278…bbc7

0x34b655…2a6f

10 touches
10 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0x95c47f03…f1bb

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x03aa8b26…118a

0x34b655…2a6f

6 touches
3 conflicts

0xd18e4cb7…88d4

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

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

10 conflicts on slot 0x2840c278a3…01bbc7

← previous block·next block →recent activity