← previous blocknext block →recent activity

Analyzing

Block #74,304,817

24 transactions · 13 stateful · 2026-05-13 10:45:24 UTC

Parallelism

79/100

Blocked

54%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,304,817  ·  24 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

0x2546fd50…aaca

0xd32edf…ff58

9 touches
10 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0x8cc18498…ce7e

0x34b655…2a6f

5 touches
3 conflicts

0xd75a2973…8af9

0x34b655…2a6f

4 touches
1 conflict

0x4d3e58e0…a2d7

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: 0xd32edf66…9fff58

10 conflicts on slot 0x2546fd50e7…0baaca

← previous block·next block →recent activity