← previous blocknext block →recent activity

Analyzing

Block #75,526,347

25 transactions · 20 stateful · 2026-05-19 02:52:49 UTC

Parallelism

80/100

Blocked

60%

Avg conflicts / tx

1.08

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,526,347  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x624ac93f…ddb0

0xd32edf…ff58

9 touches
10 conflicts

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0x313f2565…5b00

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0x8d66a4…3095

6 touches
3 conflicts

0x99f080dc…58c1

0x34b655…2a6f

5 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity