← previous blocknext block →recent activity

Analyzing

Block #94,226,487

23 transactions · 20 stateful · 2026-08-08 14:15:12 UTC

Parallelism

65/100

Blocked

55%

Avg conflicts / tx

1.3

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,226,487  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x4f3a6b4a…3819

0x34b655…2a6f

8 touches
6 conflicts

0xfe2193cc…dd74

0x34b655…2a6f

8 touches
6 conflicts

0x34cdb3c2…96d2

0x34b655…2a6f

6 touches
3 conflicts

0x3e6302c8…64f5

0x34b655…2a6f

6 touches
3 conflicts

0xa3f095f5…bd87

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

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 0xc824469a90…af6425

← previous block·next block →recent activity