← previous blocknext block →recent activity

Analyzing

Block #94,792,318

24 transactions · 21 stateful · 2026-08-10 13:54:21 UTC

Parallelism

67/100

Blocked

48%

Avg conflicts / tx

1.38

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,792,318  ·  24 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

0x0a57a2b8…3cdd

0x34b655…2a6f

12 touches
15 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

10 touches
10 conflicts

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0xc5f336ca…912e

0x34b655…2a6f

4 touches
1 conflict

0xe6043046…5757

0x34b655…2a6f

4 touches
1 conflict

0x0712100b…e8bc

0x34b655…2a6f

4 touches
1 conflict

0x0725ad1d…a03f

0x34b655…2a6f

4 touches
1 conflict

0x3c144d40…9554

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

15 conflicts on slot 0x0a57a2b8cd…773cdd

← previous block·next block →recent activity