← previous blocknext block →recent activity

Analyzing

Block #94,479,726

18 transactions · 18 stateful · 2026-08-09 11:40:38 UTC

Parallelism

61/100

Blocked

67%

Avg conflicts / tx

2.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,479,726  ·  18 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

0xb3fb9fb5…64db

0x34b655…2a6f

12 touches
15 conflicts

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xa9a54e82…3fef

0x34b655…2a6f

7 touches
6 conflicts

0x96cdbdb1…783f

0x34b655…2a6f

7 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 0xb3fb9fb561…7664db

← previous block·next block →recent activity