Block #73,210,360

← previous blocknext block →recent activity

Analyzing

Block #73,210,360

11 transactions · 10 stateful · 2026-05-08 09:04:18 UTC

Parallelism

64/100

Blocked

30%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,210,360  ·  11 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

6 touches
3 conflicts

0x5c71cf32…221f

0x065c9d…c394

4 touches
1 conflict

0x335b19b4…0900

0x065c9d…c394

3 touches
1 conflict

0xc809ca31…30ac

0x065c9d…c394

3 touches
1 conflict

0x7f189cf6…afab

0x065c9d…c394

2 touches
0 conflicts

0x70b2f813…783c

0x2a68ba…90c5

2 touches
0 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

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