← previous blocknext block →recent activity

Analyzing

Block #73,595,499

19 transactions · 14 stateful · 2026-05-10 03:46:02 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

1.37

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,595,499  ·  19 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

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x7c53af72…1e6a

0x065c9d…c394

4 touches
1 conflict

0xe795af17…a199

0x065c9d…c394

3 touches
1 conflict

0x1b1acb01…e7cf

0x065c9d…c394

3 touches
1 conflict

0xb82bffbd…c6de

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

15 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity