← previous blocknext block →recent activity

Analyzing

Block #75,478,239

39 transactions · 19 stateful · 2026-05-18 21:23:11 UTC

Parallelism

77/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,478,239  ·  39 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

0x87182544…2b78

0xd32edf…ff58

17 touches
36 conflicts

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a568

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x66de0ce3…337a

0x188d58…ea8e

2 touches
0 conflicts

0x66de0ce3…337c

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 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

36 conflicts on slot 0x8718254410…c72b78

← previous block·next block →recent activity