← previous blocknext block →recent activity

Analyzing

Block #75,479,311

28 transactions · 15 stateful · 2026-05-18 21:30:32 UTC

Parallelism

64/100

Blocked

60%

Avg conflicts / tx

1.61

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,479,311  ·  28 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xefc158af…cca9

0xd32edf…ff58

19 touches
45 conflicts

0xab2a87f1…eafb

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0003

0x094452…0a09

4 touches
1 conflict

0x00000000…0004

0x094452…0a09

4 touches
1 conflict

0x66de0ce3…337a

0x188d58…ea8e

4 touches
1 conflict

0x66de0ce3…337b

0x188d58…ea8e

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

45 conflicts on slot 0xefc158afd1…18cca9

← previous block·next block →recent activity