← previous blocknext block →recent activity

Analyzing

Block #94,962,337

20 transactions · 20 stateful · 2026-08-11 04:09:33 UTC

Parallelism

50/100

Blocked

55%

Avg conflicts / tx

1.4

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #94,962,337  ·  20 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

0xae5cb3e3…b10f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x45ea7a97…bbb3

0x34b655…2a6f

6 touches
3 conflicts

0x4b76146e…0dcb

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

15 conflicts on slot 0xae5cb3e39b…73b10f

← previous block·next block →recent activity