← previous blocknext block →recent activity

Analyzing

Block #74,765,356

40 transactions · 27 stateful · 2026-05-15 14:00:54 UTC

Parallelism

73/100

Blocked

52%

Avg conflicts / tx

1.38

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,765,356  ·  40 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xc799e56d…45aa

0x34b655…2a6f

8 touches
6 conflicts

0x9618faed…ef3d

0x34b655…2a6f

8 touches
6 conflicts

0x56a8290f…f09c

0xd32edf…ff58

7 touches
6 conflicts

0x54b965f1…42c9

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity