← previous blocknext block →recent activity

Analyzing

Block #74,761,077

40 transactions · 27 stateful · 2026-05-15 13:32:13 UTC

Parallelism

75/100

Blocked

67%

Avg conflicts / tx

1

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,761,077  ·  40 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

0x168bb3c4…8235

0xd32edf…ff58

11 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x2f77f0f6…4a92

0x188d58…ea8e

6 touches
3 conflicts

0x2f77f0f6…4a93

0x188d58…ea8e

6 touches
3 conflicts

0x33018431…8f5c

0x188d58…ea8e

6 touches
3 conflicts

0x33018431…8f5f

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0013

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

15 conflicts on slot 0x168bb3c406…648235

← previous block·next block →recent activity