← previous blocknext block →recent activity

Analyzing

Block #75,478,673

30 transactions · 19 stateful · 2026-05-18 21:26:07 UTC

Parallelism

60/100

Blocked

63%

Avg conflicts / tx

2.27

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #75,478,673  ·  30 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x4666a449…2729

0xd32edf…ff58

23 touches
66 conflicts

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0xd5b10148…e631

0x1b6862…e19c

4 touches
1 conflict

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

66 conflicts on slot 0x4666a44938…652729

← previous block·next block →recent activity