← previous blocknext block →recent activity

Analyzing

Block #74,948,860

8 transactions · 7 stateful · 2026-05-16 10:25:44 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,948,860  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x70375ad9…bee6

0x34b655…2a6f

4 touches
1 conflict

0xc389d1ff…6a00

0x34b655…2a6f

4 touches
1 conflict

0xa27fa22d…7dca

0x54cd53…9e7d

2 touches
0 conflicts

0xd1a0adf6…6e55

0x54cd53…9e7d

2 touches
0 conflicts

0x1586b16e…5b4c

0x6657d1…8ccc

2 touches
0 conflicts

0x1f373c65…8ec2

0x6657d1…8ccc

2 touches
0 conflicts

0x4091522b…5131

0x6657d1…8ccc

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: 0x34b6552d…112a6f

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity