← previous blocknext block →recent activity

Analyzing

Block #74,489,996

19 transactions · 11 stateful · 2026-05-14 07:17:40 UTC

Parallelism

84/100

Blocked

27%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,489,996  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x2734e46d…e50d

0x34b655…2a6f

6 touches
3 conflicts

0x84fb2a36…db89

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0001

0x75c3ab…4f0d

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x2734e46d30…87e50d

← previous block·next block →recent activity