← previous blocknext block →recent activity

Analyzing

Block #75,525,788

27 transactions · 18 stateful · 2026-05-19 02:49:06 UTC

Parallelism

63/100

Blocked

61%

Avg conflicts / tx

1.78

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,525,788  ·  27 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

0xd7893774…be8f

0xd32edf…ff58

19 touches
45 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x019883…2a9a

6 touches
3 conflicts

0x00000000…0002

0x019883…2a9a

6 touches
3 conflicts

0xa10c86f8…4b74

0x3bd359…433a

6 touches
3 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

6 touches
3 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 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

45 conflicts on slot 0xd78937749d…b6be8f

← previous block·next block →recent activity