← previous blocknext block →recent activity

Analyzing

Block #74,422,834

32 transactions · 20 stateful · 2026-05-13 23:50:36 UTC

Parallelism

88/100

Blocked

40%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,422,834  ·  32 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x5f258c3d…b263

0xd32edf…ff58

7 touches
6 conflicts

0xba018e2c…72cd

0x34b655…2a6f

6 touches
3 conflicts

0x28c180e1…f1e2

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

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

6 conflicts on slot 0x5f258c3dfd…2cb263

← previous block·next block →recent activity