← previous blocknext block →recent activity

Analyzing

Block #74,452,305

13 transactions · 6 stateful · 2026-05-14 03:06:50 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,452,305  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x448e04ed…9205

0x065c9d…c394

4 touches
1 conflict

0x44b77f13…c25f

0x065c9d…c394

4 touches
1 conflict

0x31a3d85b…9157

0x065c9d…c394

3 touches
1 conflict

0x0b810206…77a6

0x065c9d…c394

3 touches
1 conflict

0x0d57da06…62cb

0x065c9d…c394

2 touches
0 conflicts

0x421c43f1…894f

0x065c9d…c394

2 touches
0 conflicts

0x83e75a9f…5f0d

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

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: 0x065c9d28…a9c394

1 conflict on slot 0x448e04ed42…8c9205

← previous block·next block →recent activity