← previous blocknext block →recent activity

Analyzing

Block #94,790,721

18 transactions · 17 stateful · 2026-08-10 13:46:19 UTC

Parallelism

61/100

Blocked

59%

Avg conflicts / tx

1.39

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,790,721  ·  18 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

0x66565a2e…7c31

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc6b9bb4b…145a

0x34b655…2a6f

8 touches
6 conflicts

0x47c9eddd…356d

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x7b41d5cd…00e6

0x34b655…2a6f

6 touches
3 conflicts

0xa6176fff…d2c5

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 0x66565a2e4a…537c31

← previous block·next block →recent activity