← previous blocknext block →recent activity

Analyzing

Block #74,613,079

43 transactions · 27 stateful · 2026-05-14 21:04:30 UTC

Parallelism

86/100

Blocked

52%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,613,079  ·  43 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x30276c1c…47b4

0x2a68ba…90c5

10 touches
10 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0xb6de06bf…324d

0xd32edf…ff58

7 touches
6 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x30276c1c08…7247b4

← previous block·next block →recent activity