← previous blocknext block →recent activity

Analyzing

Block #75,501,973

32 transactions · 23 stateful · 2026-05-19 00:06:03 UTC

Parallelism

78/100

Blocked

61%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,501,973  ·  32 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x5913398f…145a

0xd32edf…ff58

11 touches
15 conflicts

0x99a21305…dffc

0x2a68ba…90c5

10 touches
10 conflicts

0x5086c64a…28ba

0x34b655…2a6f

8 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x904fc3c0…00ec

0x34b655…2a6f

4 touches
1 conflict

0xce729afd…8473

0x065c9d…c394

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

15 conflicts on slot 0x5913398f55…a3145a

← previous block·next block →recent activity