← previous blocknext block →recent activity

Analyzing

Block #73,609,865

12 transactions · 10 stateful · 2026-05-10 05:21:34 UTC

Parallelism

42/100

Blocked

60%

Avg conflicts / tx

1.58

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,609,865  ·  12 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

0x22e295f5…1bef

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x16bbffc3…8608

0x065c9d…c394

4 touches
1 conflict

0x62c27b87…f319

0x065c9d…c394

3 touches
1 conflict

0xeca8fd61…d5c4

0x065c9d…c394

3 touches
1 conflict

0x50ee3f45…94b8

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

10 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity