← previous blocknext block →recent activity

Analyzing

Block #74,765,244

36 transactions · 22 stateful · 2026-05-15 14:00:09 UTC

Parallelism

86/100

Blocked

45%

Avg conflicts / tx

0.47

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,765,244  ·  36 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x5d4f1ccc…3d87

0x34b655…2a6f

6 touches
3 conflicts

0xfb76cb70…8497

0xd32edf…ff58

5 touches
3 conflicts

0x9e0e23b5…6910

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x22e0cc1d…ad04

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

6 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity