← previous blocknext block →recent activity

Analyzing

Block #73,495,733

15 transactions · 13 stateful · 2026-05-09 16:42:56 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.93

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,495,733  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x3cb299b7…a7e2

0x065c9d…c394

2 touches
0 conflicts

0xb9b57044…c8c2

0x065c9d…c394

2 touches
0 conflicts

0xbee2bccc…d812

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0004

0x35fa64…a655

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

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity