← previous blocknext block →recent activity

Analyzing

Block #73,571,740

24 transactions · 19 stateful · 2026-05-10 01:08:02 UTC

Parallelism

75/100

Blocked

37%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,571,740  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xeaa1fb86…09c8

0xd32edf…ff58

3 touches
1 conflict

0xfe3bddd2…8b48

0x3bd359…433a

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

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: 0x065c9d28…a9c394

10 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity