Block #73,343,649

← previous blocknext block →recent activity

Analyzing

Block #73,343,649

32 transactions · 26 stateful · 2026-05-08 23:50:58 UTC

Parallelism

69/100

Blocked

54%

Avg conflicts / tx

1

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,343,649  ·  32 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x53eb2787…4830

0xd32edf…ff58

9 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x3923d7de…bb41

0x754704…b603

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