← previous blocknext block →recent activity

Analyzing

Block #73,921,002

27 transactions · 26 stateful · 2026-05-11 16:09:37 UTC

Parallelism

63/100

Blocked

65%

Avg conflicts / tx

2.19

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,921,002  ·  27 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

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

10 touches
10 conflicts

0x23951077…539b

0x34b655…2a6f

10 touches
10 conflicts

0x2aef4269…ad47

0x34b655…2a6f

10 touches
10 conflicts

0x4f483049…3cc7

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity