← previous blocknext block →recent activity

Analyzing

Block #94,857,954

17 transactions · 16 stateful · 2026-08-10 19:24:33 UTC

Parallelism

71/100

Blocked

56%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,857,954  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xec7d120d…7084

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x3eb13724…5b00

0x34b655…2a6f

4 touches
1 conflict

0xd30f9e74…d404

0x34b655…2a6f

4 touches
1 conflict

0x915c095e…c1e5

0x2b46c0…1669

2 touches
0 conflicts

0xcfe06a18…b5b5

0x2b46c0…1669

2 touches
0 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

6 conflicts on slot 0xec7d120df9…5d7084

← previous block·next block →recent activity