← previous blocknext block →recent activity

Analyzing

Block #74,610,065

26 transactions · 19 stateful · 2026-05-14 20:44:28 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,610,065  ·  26 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

0x6f3cc742…f922

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x2f7781d6…e632

0x34b655…2a6f

4 touches
1 conflict

0x4546ebad…b908

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

10 conflicts on slot 0x6f3cc7421e…edf922

← previous block·next block →recent activity