← previous blocknext block →recent activity

Analyzing

Block #75,478,699

35 transactions · 15 stateful · 2026-05-18 21:26:17 UTC

Parallelism

83/100

Blocked

53%

Avg conflicts / tx

0.66

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,478,699  ·  35 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x52e206db…c670

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0000

0x094452…0a09

6 touches
3 conflicts

0x00000000…0003

0x094452…0a09

6 touches
3 conflicts

0x00000000…0004

0x094452…0a09

6 touches
3 conflicts

0x62e20208…be65

0x0555e3…2b9c

6 touches
3 conflicts

0x9e223b01…38b2

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x58a864a6…57e3

0x754704…b603

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

15 conflicts on slot 0x52e206dbfe…edc670

← previous block·next block →recent activity