← previous blocknext block →recent activity

Analyzing

Block #74,382,916

33 transactions · 25 stateful · 2026-05-13 19:24:55 UTC

Parallelism

73/100

Blocked

56%

Avg conflicts / tx

1.45

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,382,916  ·  33 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xb5e7e005…77b7

0xd32edf…ff58

17 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x928d6b23…536f

0x1b6862…e19c

6 touches
3 conflicts

0xa02838a3…bc54

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xd40bddc1…773c

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

36 conflicts on slot 0xb5e7e0055e…f177b7

← previous block·next block →recent activity