← previous blocknext block →recent activity

Analyzing

Block #75,478,218

33 transactions · 21 stateful · 2026-05-18 21:23:02 UTC

Parallelism

76/100

Blocked

48%

Avg conflicts / tx

0.97

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,478,218  ·  33 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x912080b1…2ba3

0xd32edf…ff58

15 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8f1dbe88…8e36

0xee8c0e…1242

4 touches
1 conflict

0x53b4ef2b…8a05

0x34b655…2a6f

4 touches
1 conflict

0xda38066f…3bbe

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0000

0xca50b9…1d03

4 touches
1 conflict

0x00000000…0002

0xca50b9…1d03

4 touches
1 conflict

0x00000000…0004

0xca50b9…1d03

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

28 conflicts on slot 0x912080b12c…4d2ba3

← previous block·next block →recent activity