← previous blocknext block →recent activity

Analyzing

Block #74,482,846

16 transactions · 12 stateful · 2026-05-14 06:30:02 UTC

Parallelism

88/100

Blocked

8%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,482,846  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xa22d4a11…7c5e

0x065c9d…c394

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x161c72c7…b44a

0x065c9d…c394

2 touches
0 conflicts

0x2635e775…66b8

0x065c9d…c394

2 touches
0 conflicts

0x9cfa9237…e01d

0x065c9d…c394

2 touches
0 conflicts

0xe654e517…f4f9

0x065c9d…c394

2 touches
0 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: 0x065c9d28…a9c394

1 conflict on slot 0xa22d4a118a…a67c5e

← previous block·next block →recent activity