← previous blocknext block →recent activity

Analyzing

Block #94,667,362

25 transactions · 25 stateful · 2026-08-10 03:24:22 UTC

Parallelism

60/100

Blocked

52%

Avg conflicts / tx

1.92

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #94,667,362  ·  25 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

0xbee92963…0318

0x34b655…2a6f

12 touches
15 conflicts

0xe8d58d34…426d

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xc6b604e6…5152

0x34b655…2a6f

12 touches
15 conflicts

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0xd7908b5f…56b9

0x34b655…2a6f

8 touches
6 conflicts

0x5502e1cc…3910

0x34b655…2a6f

8 touches
6 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

15 conflicts on slot 0xbee9296354…dc0318

← previous block·next block →recent activity