← previous blocknext block →recent activity

Analyzing

Block #73,375,041

17 transactions · 16 stateful · 2026-05-09 03:19:49 UTC

Parallelism

59/100

Blocked

38%

Avg conflicts / tx

0.88

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,375,041  ·  17 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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x4841d6e9…0a18

0x065c9d…c394

2 touches
0 conflicts

0x3c514995…75cc

0x34b655…2a6f

2 touches
0 conflicts

0x64461c10…e86d

0x34b655…2a6f

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