← previous blocknext block →recent activity

Analyzing

Block #94,979,640

19 transactions · 19 stateful · 2026-08-11 05:36:34 UTC

Parallelism

47/100

Blocked

58%

Avg conflicts / tx

1.47

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #94,979,640  ·  19 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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x2b5101ac…090b

0x34b655…2a6f

10 touches
10 conflicts

0x94de4d05…ad01

0x34b655…2a6f

8 touches
6 conflicts

0x11b69a7e…334e

0x01bff4…1071

6 touches
3 conflicts

0x24b6091e…d294

0x34b655…2a6f

6 touches
3 conflicts

0x5e17e5be…d212

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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 0x482471adbb…39122f

← previous block·next block →recent activity