← previous blocknext block →recent activity

Analyzing

Block #75,478,685

42 transactions · 20 stateful · 2026-05-18 21:26:12 UTC

Parallelism

83/100

Blocked

45%

Avg conflicts / tx

0.64

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,478,685  ·  42 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x95debfa0…a177

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0000

0xca50b9…1d03

6 touches
3 conflicts

0x00000000…0004

0xca50b9…1d03

6 touches
3 conflicts

0x6320bc8e…f9a3

0xd18b7e…414b

6 touches
3 conflicts

0x8f1dbe88…8e36

0xee8c0e…1242

6 touches
3 conflicts

0x93afca4c…b478

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

21 conflicts on slot 0x95debfa0b5…84a177

← previous block·next block →recent activity