← previous blocknext block →recent activity

Analyzing

Block #73,869,275

16 transactions · 9 stateful · 2026-05-11 10:25:01 UTC

Parallelism

63/100

Blocked

56%

Avg conflicts / tx

1.13

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,869,275  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x7f81fb82…633e

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xa7fda430…cbbb

0x065c9d…c394

4 touches
1 conflict

0x7e0cf343…efab

0x065c9d…c394

4 touches
1 conflict

0x9275b31a…2253

0x065c9d…c394

2 touches
0 conflicts

0xb159af88…a9e7

0x065c9d…c394

2 touches
0 conflicts

0xb4b5d64d…2ce4

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity