← previous blocknext block →recent activity

Analyzing

Block #74,352,926

13 transactions · 12 stateful · 2026-05-13 16:05:17 UTC

Parallelism

69/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,352,926  ·  13 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

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x466f3ac7…a374

0xd32edf…ff58

3 touches
1 conflict

0x3852770e…712f

0x065c9d…c394

2 touches
0 conflicts

0x86f469ab…a0b3

0x065c9d…c394

2 touches
0 conflicts

0x9fac0303…4811

0x065c9d…c394

2 touches
0 conflicts

0xc8020c95…5843

0x065c9d…c394

2 touches
0 conflicts

0xfe2bac2b…2cec

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

3 conflicts on slot 0x47b807a243…c53307

← previous block·next block →recent activity