← previous blocknext block →recent activity

Analyzing

Block #74,509,520

38 transactions · 33 stateful · 2026-05-14 09:28:14 UTC

Parallelism

79/100

Blocked

67%

Avg conflicts / tx

1.87

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,509,520  ·  38 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

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xeb0915f1…c150

0x34b655…2a6f

10 touches
10 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

10 touches
10 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

10 touches
10 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

10 touches
10 conflicts

0x6737ee07…9978

0x34b655…2a6f

10 touches
10 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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity