← previous blocknext block →recent activity

Analyzing

Block #73,868,111

10 transactions · 8 stateful · 2026-05-11 10:17:17 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,868,111  ·  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

0x703e1383…80fa

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0xb5029e10…782c

0x065c9d…c394

3 touches
1 conflict

0x4c47d689…aa50

0x065c9d…c394

3 touches
1 conflict

0x7f81fb82…633e

0x065c9d…c394

2 touches
0 conflicts

0xbadbe31c…1b34

0x065c9d…c394

2 touches
0 conflicts

0xc1417ff1…123d

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

1 conflict on slot 0x703e13834f…cb80fa

← previous block·next block →recent activity