← previous blocknext block →recent activity

Analyzing

Block #73,395,343

14 transactions · 14 stateful · 2026-05-09 05:34:53 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

1.57

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,395,343  ·  14 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x847e8b9f…0423

0x065c9d…c394

4 touches
1 conflict

0xa1430bc5…6bc7

0x065c9d…c394

4 touches
1 conflict

0x7d7cd8ed…dcb7

0x065c9d…c394

4 touches
1 conflict

0xa5c22cce…7e46

0x065c9d…c394

4 touches
1 conflict

0xfcaea661…bd93

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

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity