← previous blocknext block →recent activity

Analyzing

Block #73,490,796

24 transactions · 23 stateful · 2026-05-09 16:10:11 UTC

Parallelism

54/100

Blocked

57%

Avg conflicts / tx

2.46

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,490,796  ·  24 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

16 touches
28 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x22e295f5…1bef

0x065c9d…c394

12 touches
15 conflicts

0x6f08361d…bda6

0x065c9d…c394

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x1dc31650…6566

0x065c9d…c394

4 touches
2 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

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

28 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity