← previous blocknext block →recent activity

Analyzing

Block #73,640,732

15 transactions · 14 stateful · 2026-05-10 08:48:47 UTC

Parallelism

53/100

Blocked

43%

Avg conflicts / tx

1.27

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,640,732  ·  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

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x3c36f470…e2b3

0x065c9d…c394

4 touches
1 conflict

0xc8189db0…440b

0x065c9d…c394

3 touches
1 conflict

0x5a471555…a44b

0x065c9d…c394

3 touches
1 conflict

0xbb38808f…b1ee

0x065c9d…c394

2 touches
0 conflicts

0xf0ca1c42…03da

0x065c9d…c394

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 0x0000000000…00003d

← previous block·next block →recent activity