← previous blocknext block →recent activity

Analyzing

Block #74,457,027

17 transactions · 12 stateful · 2026-05-14 03:38:20 UTC

Parallelism

76/100

Blocked

25%

Avg conflicts / tx

0.24

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,457,027  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0xd0675a89…a9a3

0x34b655…2a6f

4 touches
1 conflict

0xfe3d37ee…6e67

0x34b655…2a6f

4 touches
1 conflict

0x83e75a9f…5f0d

0x065c9d…c394

2 touches
0 conflicts

0x86bb8737…ba02

0x065c9d…c394

2 touches
0 conflicts

0xe02ea065…d55c

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity