← previous blocknext block →recent activity

Analyzing

Block #75,478,613

21 transactions · 17 stateful · 2026-05-18 21:25:43 UTC

Parallelism

52/100

Blocked

65%

Avg conflicts / tx

1.62

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,478,613  ·  21 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

0x4793ef7f…0e4b

0xd32edf…ff58

15 touches
28 conflicts

0x5f77d607…2c84

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xe01158fd…f97c

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

28 conflicts on slot 0x4793ef7fcf…340e4b

← previous block·next block →recent activity