← previous blocknext block →recent activity

Analyzing

Block #94,950,924

23 transactions · 21 stateful · 2026-08-11 03:12:09 UTC

Parallelism

65/100

Blocked

48%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,950,924  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x216ffe66…1f94

0x34b655…2a6f

8 touches
6 conflicts

0x1a5d321d…a474

0x34b655…2a6f

6 touches
3 conflicts

0xf6a5426d…8280

0x34b655…2a6f

6 touches
3 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x8c7321a1…a72d

0x34b655…2a6f

6 touches
3 conflicts

0xac3e4969…39e9

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity