← previous blocknext block →recent activity

Analyzing

Block #74,234,339

7 transactions · 6 stateful · 2026-05-13 02:56:43 UTC

Parallelism

71/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,234,339  ·  7 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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1a2

0x8d66a4…3095

4 touches
1 conflict

0x7f430e47…4cbd

0x8d66a4…3095

3 touches
1 conflict

0x2f5dbf2f…08d9

0x065c9d…c394

2 touches
0 conflicts

0xe500ddd8…26a7

0x065c9d…c394

2 touches
0 conflicts

0xeb53e905…8002

0x065c9d…c394

2 touches
0 conflicts

0xffc055d7…ddca

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

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity