← previous blocknext block →recent activity

Analyzing

Block #74,481,001

13 transactions · 12 stateful · 2026-05-14 06:17:46 UTC

Parallelism

85/100

Blocked

8%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,481,001  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xc3aacf13…6b3d

0x34b655…2a6f

4 touches
1 conflict

0x220f4f84…15f8

0x34b655…2a6f

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

0x065c9d…c394

2 touches
0 conflicts

0x262bb27b…6b2c

0x11ed3b…2c96

2 touches
0 conflicts

0x0872abbe…9c39

0x2a68ba…90c5

2 touches
0 conflicts

0x76e559a4…77fb

0x2a68ba…90c5

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

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 0xc3aacf13f1…5d6b3d

← previous block·next block →recent activity