← previous blocknext block →recent activity

Analyzing

Block #74,459,709

22 transactions · 14 stateful · 2026-05-14 03:56:10 UTC

Parallelism

82/100

Blocked

21%

Avg conflicts / tx

0.18

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,459,709  ·  22 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

0xedb848fe…6534

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0x8a85cf3d…2868

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xde3a7f3a…8480

0x34b655…2a6f

4 touches
1 conflict

0x2f77f0f6…4a93

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5c

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5e

0x188d58…ea8e

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 0xedb848fed2…6e6534

← previous block·next block →recent activity