← previous blocknext block →recent activity

Analyzing

Block #73,386,857

10 transactions · 10 stateful · 2026-05-09 04:38:24 UTC

Parallelism

70/100

Blocked

30%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,386,857  ·  10 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

0x3f275294…f60e

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x94e1c0c4…f496

0x065c9d…c394

3 touches
1 conflict

0x32a82524…fb30

0x065c9d…c394

3 touches
1 conflict

0x3c0b1f29…d396

0x065c9d…c394

2 touches
0 conflicts

0x57b13b62…2f75

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: 0x065c9d28…a9c394

1 conflict on slot 0x3f275294e1…a4f60e

← previous block·next block →recent activity