← previous blocknext block →recent activity

Analyzing

Block #74,571,975

27 transactions · 19 stateful · 2026-05-14 16:29:24 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,571,975  ·  27 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xa1807d72…d3f7

0xd32edf…ff58

9 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0x38a06385…ed6a

0x34b655…2a6f

4 touches
1 conflict

0x3b4d64bb…c98d

0x34b655…2a6f

4 touches
1 conflict

0x454cdf57…aebc

0x34b655…2a6f

4 touches
1 conflict

0x4ae42034…49ca

0x34b655…2a6f

4 touches
1 conflict

0x4db74a88…1c46

0x34b655…2a6f

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

10 conflicts on slot 0xa1807d7260…76d3f7

← previous block·next block →recent activity