← previous blocknext block →recent activity

Analyzing

Block #75,519,080

21 transactions · 14 stateful · 2026-05-19 02:03:09 UTC

Parallelism

86/100

Blocked

21%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,519,080  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xc5136ce9…41c1

0xd32edf…ff58

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x5f77d607…2c84

0x065c9d…c394

2 touches
0 conflicts

0xd366adcd…cde3

0x065c9d…c394

2 touches
0 conflicts

0x99a21305…dffc

0x2a68ba…90c5

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

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: 0x34b6552d…112a6f

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity