← previous blocknext block →recent activity

Analyzing

Block #75,478,595

46 transactions · 26 stateful · 2026-05-18 21:25:36 UTC

Parallelism

76/100

Blocked

58%

Avg conflicts / tx

1.41

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,478,595  ·  46 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

0xe91d68f9…4735

0xd32edf…ff58

21 touches
55 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0002

0x019883…2a9a

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0xa24d15eb…cc92

0x0555e3…2b9c

4 touches
1 conflict

0x44ad89ba…cf83

0x0cc9b2…7777

4 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a567

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 0xe91d68f924…f04735

← previous block·next block →recent activity