← previous blocknext block →recent activity

Analyzing

Block #74,040,813

25 transactions · 20 stateful · 2026-05-12 05:29:13 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1.28

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,040,813  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x00000000…0001

0x5c533c…a5a6

16 touches
28 conflicts

0x64538394…fdae

0xd32edf…ff58

5 touches
3 conflicts

0xd53220ed…4737

0x1b6862…e19c

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x39429ff6…2385

0x34b655…2a6f

4 touches
1 conflict

0x4599ceea…e18c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdaca243a…f9de

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: 0x5c533c7f…5ba5a6

28 conflicts on slot 0x0000000000…000001

← previous block·next block →recent activity