← previous blocknext block →recent activity

Analyzing

Block #73,846,158

8 transactions · 8 stateful · 2026-05-11 07:50:46 UTC

Parallelism

50/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,846,158  ·  8 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

0xa295e8d1…5a55

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xbca435e9…f283

0x065c9d…c394

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x616f94b2…2953

0x065c9d…c394

3 touches
1 conflict

0xa5e794a6…4886

0x065c9d…c394

3 touches
1 conflict

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 0xa295e8d1d1…145a55

← previous block·next block →recent activity