← previous blocknext block →recent activity

Analyzing

Block #74,210,253

26 transactions · 13 stateful · 2026-05-13 00:16:29 UTC

Parallelism

81/100

Blocked

31%

Avg conflicts / tx

0.38

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,210,253  ·  26 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

0xf3c47389…c6d9

0xd32edf…ff58

9 touches
10 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…0000

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…0002

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…0003

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…0005

0x1397bd…f779

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

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

10 conflicts on slot 0xf3c473892e…5cc6d9

← previous block·next block →recent activity