← previous blocknext block →recent activity

Analyzing

Block #94,201,228

21 transactions · 14 stateful · 2026-08-08 12:07:16 UTC

Parallelism

86/100

Blocked

43%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,201,228  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x0dd3d3cd…7281

0x34b655…2a6f

6 touches
3 conflicts

0xc2403164…b6d3

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x74f95963…01a2

0x34b655…2a6f

6 touches
3 conflicts

0x5dc2039b…8a19

0x34b655…2a6f

4 touches
1 conflict

0x70986451…c6bd

0x34b655…2a6f

4 touches
1 conflict

0x7c524e26…54c6

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

3 conflicts on slot 0x0dd3d3cd18…c87281

← previous block·next block →recent activity