← previous blocknext block →recent activity

Analyzing

Block #74,645,064

10 transactions · 9 stateful · 2026-05-15 00:37:45 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,645,064  ·  10 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

0x59bf920c…3c0b

0x065c9d…c394

4 touches
1 conflict

0x660e1c89…c98c

0x065c9d…c394

3 touches
1 conflict

0x962037e0…41c3

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0xb12ed9f2…6d70

0x065c9d…c394

2 touches
0 conflicts

0xbeec2a43…de31

0x065c9d…c394

2 touches
0 conflicts

0x00000000…000b

0x2a347b…e9d3

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 0x59bf920cb7…9b3c0b

← previous block·next block →recent activity