← previous blocknext block →recent activity

Analyzing

Block #74,466,369

25 transactions · 14 stateful · 2026-05-14 04:40:31 UTC

Parallelism

72/100

Blocked

57%

Avg conflicts / tx

0.8

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,466,369  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf3981be5…2c47

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbc04d98e…a484

0x34b655…2a6f

6 touches
3 conflicts

0xcb63cb0a…66a9

0x34b655…2a6f

6 touches
3 conflicts

0x4118ae27…23f9

0x34b655…2a6f

4 touches
1 conflict

0x4582e32d…1abe

0x34b655…2a6f

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

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

15 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity