← previous blocknext block →recent activity

Analyzing

Block #75,685,605

44 transactions · 18 stateful · 2026-05-19 20:35:16 UTC

Parallelism

75/100

Blocked

61%

Avg conflicts / tx

1.27

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,685,605  ·  44 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xff33d2dd…4802

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xae08b504…d655

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c3

0x1b6862…e19c

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

55 conflicts on slot 0xff33d2ddd7…234802

← previous block·next block →recent activity