← previous blocknext block →recent activity

Analyzing

Block #73,867,362

15 transactions · 10 stateful · 2026-05-11 10:12:18 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,867,362  ·  15 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x020d42d0…43c5

0x188d58…ea8e

2 touches
0 conflicts

0x6f95bb81…75df

0x188d58…ea8e

2 touches
0 conflicts

0x6f95bb81…75e0

0x188d58…ea8e

2 touches
0 conflicts

0xe75ce681…ba62

0x188d58…ea8e

2 touches
0 conflicts

0xe7bc0e8a…f536

0x188d58…ea8e

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity