← previous blocknext block →recent activity

Analyzing

Block #74,402,911

15 transactions · 8 stateful · 2026-05-13 21:38:03 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,402,911  ·  15 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

0xc684c7fc…0547

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x9b36f19f…fa5a

0x34b655…2a6f

4 touches
1 conflict

0xa05dafe7…aff6

0x34b655…2a6f

4 touches
1 conflict

0xef17b8cd…9511

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0x310a7246…2dcb

0x34b655…2a6f

4 touches
1 conflict

0xd40bddc1…773c

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

1 conflict on slot 0xc684c7fc22…690547

← previous block·next block →recent activity