← previous blocknext block →recent activity

Analyzing

Block #73,210,072

17 transactions · 16 stateful · 2026-05-08 09:02:23 UTC

Parallelism

76/100

Blocked

19%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,210,072  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xce7bfe5e…5e58

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2b342fce…7006

0x065c9d…c394

4 touches
1 conflict

0x47e026b0…0f57

0x065c9d…c394

3 touches
1 conflict

0xaa5d4a5f…a80c

0x065c9d…c394

3 touches
1 conflict

0x4cb81726…ef8f

0x065c9d…c394

2 touches
0 conflicts

0x814e73f6…d628

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