← previous blocknext block →recent activity

Analyzing

Block #73,270,821

16 transactions · 14 stateful · 2026-05-08 15:46:26 UTC

Parallelism

81/100

Blocked

21%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,270,821  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x5e54c4f9…81c8

0x065c9d…c394

2 touches
0 conflicts

0x650bd02e…1771

0x065c9d…c394

2 touches
0 conflicts

0x6a48363e…1d05

0x065c9d…c394

2 touches
0 conflicts

0xd11b0a03…ddbe

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity