← previous blocknext block →recent activity

Analyzing

Block #94,834,713

18 transactions · 16 stateful · 2026-08-10 17:27:38 UTC

Parallelism

72/100

Blocked

38%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,834,713  ·  18 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

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd30f9e74…d404

0x34b655…2a6f

6 touches
3 conflicts

0x28ceceef…ecc2

0x34b655…2a6f

4 touches
1 conflict

0x58d0a23c…5d3a

0x34b655…2a6f

4 touches
1 conflict

0x3464bbc5…a323

0xa6afd3…d132

4 touches
1 conflict

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0x07d8b1e8…78c6

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

6 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity