← previous blocknext block →recent activity

Analyzing

Block #74,331,492

31 transactions · 23 stateful · 2026-05-13 13:42:48 UTC

Parallelism

84/100

Blocked

48%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,331,492  ·  31 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xb2453cd6…4c97

0xd32edf…ff58

7 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x016bd8f2…c85a

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xc1f28224…cb43

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a5

0x8d66a4…3095

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

6 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity