← previous blocknext block →recent activity

Analyzing

Block #74,484,565

36 transactions · 21 stateful · 2026-05-14 06:41:30 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,484,565  ·  36 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x1876589a…d1be

0xd32edf…ff58

11 touches
15 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xd6aabe89…92f5

0x34b655…2a6f

5 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0xdef19d99…c0a9

0x34b655…2a6f

3 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: 0xd32edf66…9fff58

15 conflicts on slot 0x1876589a43…48d1be

← previous block·next block →recent activity