← previous blocknext block →recent activity

Analyzing

Block #75,479,314

27 transactions · 15 stateful · 2026-05-18 21:30:33 UTC

Parallelism

63/100

Blocked

60%

Avg conflicts / tx

1.67

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,479,314  ·  27 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

0x42cb3a4d…9ed7

0xd32edf…ff58

19 touches
45 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a567

0x188d58…ea8e

2 touches
0 conflicts

0x66de0ce3…337a

0x188d58…ea8e

2 touches
0 conflicts

0x66de0ce3…337b

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 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

45 conflicts on slot 0x42cb3a4d96…539ed7

← previous block·next block →recent activity