← previous blocknext block →recent activity

Analyzing

Block #94,795,146

19 transactions · 16 stateful · 2026-08-10 14:08:34 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,795,146  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xb4ec9133…495f

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xbeedaa05…9eda

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x4abfb389…18f4

0x34b655…2a6f

6 touches
3 conflicts

0x30ae635d…5e67

0x34b655…2a6f

6 touches
3 conflicts

0x43fd3667…094b

0x34b655…2a6f

4 touches
1 conflict

0x55eef346…d185

0x34b655…2a6f

4 touches
1 conflict

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 0xb4ec91339c…49495f

← previous block·next block →recent activity