← previous blocknext block →recent activity

Analyzing

Block #75,104,849

18 transactions · 11 stateful · 2026-05-17 03:48:06 UTC

Parallelism

78/100

Blocked

45%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,104,849  ·  18 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

0x3eb7a384…179b

0xd32edf…ff58

7 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x25f0fcba…ca8b

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xd6aabe89…92f5

0x34b655…2a6f

5 touches
3 conflicts

0xef17b8cd…9511

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: 0xd32edf66…9fff58

6 conflicts on slot 0x3eb7a384ca…91179b

← previous block·next block →recent activity