← previous blocknext block →recent activity

Analyzing

Block #74,643,700

19 transactions · 14 stateful · 2026-05-15 00:28:39 UTC

Parallelism

79/100

Blocked

50%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,643,700  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf6354bfa…ca25

0xd32edf…ff58

7 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0x2d5e3771…9a87

0x34b655…2a6f

4 touches
1 conflict

0x867030aa…a98f

0x065c9d…c394

4 touches
1 conflict

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x53b4ef2b…8a05

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

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

6 conflicts on slot 0xf6354bfa12…56ca25

← previous block·next block →recent activity