← previous blocknext block →recent activity

Analyzing

Block #94,901,158

22 transactions · 21 stateful · 2026-08-10 23:01:51 UTC

Parallelism

68/100

Blocked

48%

Avg conflicts / tx

1.41

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,901,158  ·  22 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

0xac2a0273…721b

0x34b655…2a6f

14 touches
21 conflicts

0x737acb78…fce8

0x34b655…2a6f

12 touches
15 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x11258774…9892

0x2a68ba…90c5

6 touches
3 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xce06a0f7…efef

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

21 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity