← previous blocknext block →recent activity

Analyzing

Block #74,460,709

27 transactions · 19 stateful · 2026-05-14 04:02:48 UTC

Parallelism

78/100

Blocked

53%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,460,709  ·  27 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0x12309510…0ac2

0x000000…012a

8 touches
6 conflicts

0x33018431…8f5c

0x188d58…ea8e

8 touches
6 conflicts

0x7cee1be1…e770

0x34b655…2a6f

6 touches
3 conflicts

0x33018431…8f5e

0x188d58…ea8e

6 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity