← previous blocknext block →recent activity

Analyzing

Block #74,744,948

31 transactions · 22 stateful · 2026-05-15 11:44:12 UTC

Parallelism

77/100

Blocked

41%

Avg conflicts / tx

0.81

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,744,948  ·  31 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x34c0b99c…b4c5

0xd32edf…ff58

13 touches
21 conflicts

0xea57afd0…4232

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x14969d4c…14e2

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x726913e2…0e14

0x34b655…2a6f

4 touches
1 conflict

0xd6aabe89…92f5

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

21 conflicts on slot 0x34c0b99c6d…4ab4c5

← previous block·next block →recent activity