← previous blocknext block →recent activity

Analyzing

Block #73,297,358

24 transactions · 15 stateful · 2026-05-08 18:42:59 UTC

Parallelism

88/100

Blocked

33%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,297,358  ·  24 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

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0xfff38d9f…7063

0x8d66a4…3095

4 touches
1 conflict

0xbe51982e…ee9b

0xa6afd3…d132

4 touches
1 conflict

0x0dbf9688…c6cf

0xd18b7e…414b

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

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