← previous blocknext block →recent activity

Analyzing

Block #75,501,992

48 transactions · 30 stateful · 2026-05-19 00:06:10 UTC

Parallelism

83/100

Blocked

53%

Avg conflicts / tx

1.04

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,501,992  ·  48 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x8017272a…23e0

0xd32edf…ff58

15 touches
28 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xce8bbe33…b72e

0x3bd359…433a

10 touches
10 conflicts

0x6af306bb…2e81

0x3bd359…433a

10 touches
10 conflicts

0xf91b744e…9117

0x754704…b603

10 touches
10 conflicts

0xe937b6bc…8a54

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

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

28 conflicts on slot 0x8017272aaa…3a23e0

← previous block·next block →recent activity