← previous blocknext block →recent activity

Analyzing

Block #74,601,374

22 transactions · 13 stateful · 2026-05-14 19:46:18 UTC

Parallelism

91/100

Blocked

31%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,601,374  ·  22 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0xbbac368f…30db

0x34b655…2a6f

4 touches
1 conflict

0xce3d666c…99c5

0x34b655…2a6f

4 touches
1 conflict

0xd32f8498…be67

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3808e5a…dbfb

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: 0xc8689a47…62ee79

1 conflict on slot 0x35b65947f9…9a44d1

← previous block·next block →recent activity