← previous blocknext block →recent activity

Analyzing

Block #74,267,119

14 transactions · 12 stateful · 2026-05-13 06:34:36 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.36

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,267,119  ·  14 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

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb9d2cf20…a668

0x34b655…2a6f

4 touches
1 conflict

0xc018f388…c875

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x7613eaeb…7bb6

0x065c9d…c394

2 touches
0 conflicts

0x77ee54d0…f56e

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 0x24968e6db4…f00132

← previous block·next block →recent activity