← previous blocknext block →recent activity

Analyzing

Block #75,478,957

26 transactions · 17 stateful · 2026-05-18 21:28:02 UTC

Parallelism

65/100

Blocked

59%

Avg conflicts / tx

1.23

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,478,957  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x07812903…536b

0xd32edf…ff58

15 touches
28 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

6 touches
3 conflicts

0x00f7e3b7…e016

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

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

28 conflicts on slot 0x0781290318…b8536b

← previous block·next block →recent activity