← previous blocknext block →recent activity

Analyzing

Block #74,456,090

14 transactions · 10 stateful · 2026-05-14 03:32:05 UTC

Parallelism

86/100

Blocked

10%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,456,090  ·  14 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

0x786f590a…b1b4

0x065c9d…c394

4 touches
1 conflict

0xf12b7a9c…c0a7

0x065c9d…c394

3 touches
1 conflict

0x5750e3c6…73c0

0x065c9d…c394

3 touches
1 conflict

0x26af1b06…f8b7

0x065c9d…c394

2 touches
0 conflicts

0x286fd7f0…7592

0x065c9d…c394

2 touches
0 conflicts

0x9999108f…b1a9

0x065c9d…c394

2 touches
0 conflicts

0xb18263db…2196

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x786f590a6e…ecb1b4

← previous block·next block →recent activity