← previous blocknext block →recent activity

Analyzing

Block #74,601,739

14 transactions · 12 stateful · 2026-05-14 19:48:51 UTC

Parallelism

79/100

Blocked

17%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,601,739  ·  14 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

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xb5e92bf8…4138

0x34b655…2a6f

4 touches
1 conflict

0xbc04d98e…a484

0x34b655…2a6f

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

2 touches
0 conflicts

0xca274f09…fcec

0x065c9d…c394

2 touches
0 conflicts

0xf282d38a…cfae

0x065c9d…c394

2 touches
0 conflicts

0xf5dedfc5…2f67

0x065c9d…c394

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

3 conflicts on slot 0xfe3d37ee7e…836e67

← previous block·next block →recent activity