← previous blocknext block →recent activity

Analyzing

Block #85,426,196

22 transactions · 20 stateful · 2026-07-03 23:21:09 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,426,196  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xf06ab8d8…3589

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

6 touches
3 conflicts

0x30faf03c…78b1

0x34b655…2a6f

6 touches
3 conflicts

0x2c8bf7d9…3cc7

0xc8689a…ee79

4 touches
1 conflict

0x15a8dcd6…2c36

0x34b655…2a6f

4 touches
1 conflict

0x15c9b5bf…f732

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 0xfaef08b108…f90696

← previous block·next block →recent activity