← previous blocknext block →recent activity

Analyzing

Block #74,765,275

19 transactions · 13 stateful · 2026-05-15 14:00:21 UTC

Parallelism

84/100

Blocked

23%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,765,275  ·  19 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

0x676f9f01…a8ac

0x34b655…2a6f

6 touches
3 conflicts

0x145554b9…8b5f

0x34b655…2a6f

4 touches
1 conflict

0x1c1b5ec9…43f6

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x8fbde2b3…9b8f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…401e

0x34b655…2a6f

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 0x676f9f01ee…dea8ac

← previous block·next block →recent activity