← previous blocknext block →recent activity

Analyzing

Block #75,478,687

30 transactions · 16 stateful · 2026-05-18 21:26:12 UTC

Parallelism

63/100

Blocked

75%

Avg conflicts / tx

2

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,478,687  ·  30 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

0x605260cb…bc86

0xd32edf…ff58

21 touches
55 conflicts

0x846f2172…fd54

0x0555e3…2b9c

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a567

0x188d58…ea8e

4 touches
1 conflict

0x66de0ce3…337a

0x188d58…ea8e

4 touches
1 conflict

0x76415c3e…1ad9

0x188d58…ea8e

4 touches
1 conflict

0x76415c3e…1ada

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

55 conflicts on slot 0x605260cbdc…06bc86

← previous block·next block →recent activity