← previous blocknext block →recent activity

Analyzing

Block #74,506,837

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

Parallelism

89/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,506,837  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x5aed1bd2…7afa

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xc12b04b0…884b

0x34b655…2a6f

3 touches
1 conflict

0x1a606974…71ae

0x065c9d…c394

2 touches
0 conflicts

0x5b9804ba…d351

0x065c9d…c394

2 touches
0 conflicts

0x5c01350e…ff57

0x065c9d…c394

2 touches
0 conflicts

0x72a3dcc1…684d

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity