← previous blocknext block →recent activity

Analyzing

Block #74,944,869

15 transactions · 11 stateful · 2026-05-16 09:58:54 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,944,869  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe54a1f6f…18f2

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x9dc9fa5f…7f23

0x34b655…2a6f

6 touches
3 conflicts

0xaa0d0542…d8ec

0x34b655…2a6f

6 touches
3 conflicts

0x8b31e1d0…b6d1

0x34b655…2a6f

6 touches
3 conflicts

0x7cbd466f…1700

0x34b655…2a6f

4 touches
1 conflict

0x8a85cf3d…2868

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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

10 conflicts on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity