← previous blocknext block →recent activity

Analyzing

Block #73,808,570

8 transactions · 7 stateful · 2026-05-11 03:40:40 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,808,570  ·  8 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

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x0ae3f4cd…3c2b

0x065c9d…c394

3 touches
1 conflict

0x9ce240bd…b837

0xa6afd3…d132

3 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

2 touches
0 conflicts

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0x79bd3c69…38e1

0x065c9d…c394

2 touches
0 conflicts

0x88b4c5f8…3d7f

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

1 conflict on slot 0xa4e3b3b1bb…130911

← previous block·next block →recent activity