← previous blocknext block →recent activity

Analyzing

Block #73,348,274

20 transactions · 17 stateful · 2026-05-09 00:21:45 UTC

Parallelism

80/100

Blocked

29%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,348,274  ·  20 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

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xcf17589f…048c

0x34b655…2a6f

4 touches
1 conflict

0x948cb6af…d5b3

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xbdff944d…447e

0x2a68ba…90c5

4 touches
1 conflict

0x4bef88e0…eaca

0x3bd359…433a

2 touches
0 conflicts

0xfbcfe8ee…8137

0x3bd359…433a

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

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity