← previous blocknext block →recent activity

Analyzing

Block #75,525,813

23 transactions · 15 stateful · 2026-05-19 02:49:16 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.78

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,525,813  ·  23 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

0x0c300c40…1265

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0x892daf6e…48d8

0x065c9d…c394

4 touches
1 conflict

0xdb9d8189…e926

0xa6afd3…d132

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 0x0c300c40b4…951265

← previous block·next block →recent activity