← previous blocknext block →recent activity

Analyzing

Block #74,459,798

19 transactions · 16 stateful · 2026-05-14 03:56:46 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,459,798  ·  19 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

0x32c7c27b…3479

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x0a85a226…83be

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x38aa1898…fdf5

0x1b6862…e19c

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

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

21 conflicts on slot 0x32c7c27b1d…743479

← previous block·next block →recent activity