← previous blocknext block →recent activity

Analyzing

Block #75,525,790

20 transactions · 15 stateful · 2026-05-19 02:49:07 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,525,790  ·  20 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

0xa596ea08…ec16

0xd32edf…ff58

9 touches
10 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x22bdb074…20b1

0x34b655…2a6f

6 touches
3 conflicts

0xfd784183…67bb

0x34b655…2a6f

5 touches
3 conflicts

0xd5b10148…e632

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xa4e3b3b1…0911

0x2a68ba…90c5

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

10 conflicts on slot 0xa596ea0886…01ec16

← previous block·next block →recent activity