← previous blocknext block →recent activity

Analyzing

Block #73,987,179

8 transactions · 6 stateful · 2026-05-11 23:30:58 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,987,179  ·  8 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

0xfb96aa8e…a6fb

0xd32edf…ff58

3 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x196569c1…55d1

0x065c9d…c394

2 touches
0 conflicts

0x1ba85df7…5be7

0x065c9d…c394

2 touches
0 conflicts

0x30a6b0d6…d52a

0x065c9d…c394

2 touches
0 conflicts

0x4c907e02…c824

0x065c9d…c394

2 touches
0 conflicts

0x4f93947a…05ae

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: 0xd32edf66…9fff58

1 conflict on slot 0xfb96aa8e75…0ca6fb

← previous block·next block →recent activity