← previous blocknext block →recent activity

Analyzing

Block #75,098,093

37 transactions · 32 stateful · 2026-05-17 03:03:01 UTC

Parallelism

78/100

Blocked

66%

Avg conflicts / tx

1.43

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,098,093  ·  37 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

0xb42574b9…64a4

0xd32edf…ff58

15 touches
28 conflicts

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xea2d3331…6e31

0x1b6862…e19c

6 touches
3 conflicts

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 0xb42574b9f7…3464a4

← previous block·next block →recent activity