← previous blocknext block →recent activity

Analyzing

Block #74,215,490

18 transactions · 14 stateful · 2026-05-13 00:51:22 UTC

Parallelism

72/100

Blocked

29%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,215,490  ·  18 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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x8496aa9d…7f23

0x065c9d…c394

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x1b159f3d…9163

0x34b655…2a6f

2 touches
0 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

2 touches
0 conflicts

0x768cffcd…2648

0x34b655…2a6f

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity