← previous blocknext block →recent activity

Analyzing

Block #77,238,819

21 transactions · 17 stateful · 2026-05-27 01:02:01 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #77,238,819  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x9e719c7a…df63

0x34b655…2a6f

6 touches
3 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x839c0c71…bada

0x34b655…2a6f

6 touches
3 conflicts

0xe8aab7db…a319

0xa6afd3…d132

6 touches
3 conflicts

0x69ffaca0…232d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity