← previous blocknext block →recent activity

Analyzing

Block #73,501,651

22 transactions · 21 stateful · 2026-05-09 17:22:23 UTC

Parallelism

59/100

Blocked

43%

Avg conflicts / tx

1.82

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,501,651  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x00000000…003d

0x065c9d…c394

16 touches
28 conflicts

0x22e295f5…1bef

0x065c9d…c394

12 touches
15 conflicts

0x4d87512b…897c

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0xc6147686…98fc

0x065c9d…c394

4 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

28 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity