← previous blocknext block →recent activity

Analyzing

Block #94,868,281

20 transactions · 19 stateful · 2026-08-10 20:16:30 UTC

Parallelism

60/100

Blocked

47%

Avg conflicts / tx

0.85

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,868,281  ·  20 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

0xa0c9bb84…ba20

0x34b655…2a6f

6 touches
3 conflicts

0xc751242c…efac

0x34b655…2a6f

6 touches
3 conflicts

0x216ffe66…1f94

0x34b655…2a6f

6 touches
3 conflicts

0x5fab7fbe…1ce5

0x34b655…2a6f

6 touches
3 conflicts

0x94de4d05…ad01

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xb5924647…4cf1

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

3 conflicts on slot 0xa0c9bb84f1…e2ba20

← previous block·next block →recent activity