← previous blocknext block →recent activity

Analyzing

Block #94,481,148

18 transactions · 18 stateful · 2026-08-09 11:47:47 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.17

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #94,481,148  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x78ea1843…50f7

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x06bedcc7…2001

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xd66696e0…0842

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 0x78ea1843e0…cf50f7

← previous block·next block →recent activity