← previous blocknext block →recent activity

Analyzing

Block #74,331,385

28 transactions · 20 stateful · 2026-05-13 13:42:08 UTC

Parallelism

86/100

Blocked

40%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,331,385  ·  28 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

0xcafa2040…d440

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x11560115…bfc2

0x34b655…2a6f

4 touches
1 conflict

0x2f7781d6…e632

0x34b655…2a6f

4 touches
1 conflict

0x3347cbe5…846c

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

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

3 conflicts on slot 0xcafa20409d…d4d440

← previous block·next block →recent activity