← previous blocknext block →recent activity

Analyzing

Block #73,395,324

15 transactions · 14 stateful · 2026-05-09 05:34:45 UTC

Parallelism

53/100

Blocked

50%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,395,324  ·  15 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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x489b4586…883d

0x065c9d…c394

4 touches
1 conflict

0x7d7cd8ed…dcb7

0x065c9d…c394

4 touches
1 conflict

0xa5c22cce…7e46

0x065c9d…c394

4 touches
1 conflict

0xb81d3ee7…3947

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity