← previous blocknext block →recent activity

Analyzing

Block #74,503,870

18 transactions · 12 stateful · 2026-05-14 08:50:10 UTC

Parallelism

89/100

Blocked

8%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,503,870  ·  18 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

0xe181f491…f4e3

0x34b655…2a6f

4 touches
1 conflict

0xab621973…cc16

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x76cdcdd0…3f23

0x065c9d…c394

2 touches
0 conflicts

0x84697bc7…6049

0x065c9d…c394

2 touches
0 conflicts

0x9cfa9237…e01d

0x065c9d…c394

2 touches
0 conflicts

0xfd475b8a…9439

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: 0x34b6552d…112a6f

1 conflict on slot 0xe181f491d8…b1f4e3

← previous block·next block →recent activity