← previous blocknext block →recent activity

Analyzing

Block #74,456,929

15 transactions · 13 stateful · 2026-05-14 03:37:41 UTC

Parallelism

73/100

Blocked

23%

Avg conflicts / tx

0.27

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,456,929  ·  15 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x63d7ebf0…3dd9

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x575679d9…bf10

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x5d64bf0d…348f

0x065c9d…c394

2 touches
0 conflicts

0xc68b83b8…7afd

0x065c9d…c394

2 touches
0 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: 0x34b6552d…112a6f

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity