← previous blocknext block →recent activity

Analyzing

Block #75,309,695

21 transactions · 18 stateful · 2026-05-18 02:37:03 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

1.14

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,309,695  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xe8aa987b…a16f

0xd32edf…ff58

11 touches
15 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

6 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb85

0x1b6862…e19c

4 touches
1 conflict

0x968bdacb…f461

0x2a68ba…90c5

4 touches
1 conflict

0x99a21305…dffc

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

15 conflicts on slot 0xe8aa987b84…eca16f

← previous block·next block →recent activity