← previous blocknext block →recent activity

Analyzing

Block #74,442,868

9 transactions · 9 stateful · 2026-05-14 02:04:04 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,442,868  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xfe3d37ee…6e67

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0d2947c3…98d6

0x34b655…2a6f

4 touches
1 conflict

0x5f450515…3bc4

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x6dd62d2b…f17e

0x34b655…2a6f

2 touches
0 conflicts

0x904fc3c0…00ec

0x34b655…2a6f

2 touches
0 conflicts

0xc08384da…ecb7

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

1 conflict on slot 0xfe3d37ee7e…836e67

← previous block·next block →recent activity