← previous blocknext block →recent activity

Analyzing

Block #73,960,779

19 transactions · 18 stateful · 2026-05-11 20:34:07 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

1.47

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,960,779  ·  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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x6f08361d…bda6

0x065c9d…c394

10 touches
10 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0000

0x41be85…e2bd

6 touches
3 conflicts

0x00000000…0001

0x41be85…e2bd

6 touches
3 conflicts

0x072430d8…35ad

0xed8924…7777

6 touches
3 conflicts

0x44ad89ba…cf83

0xed8924…7777

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

← previous block·next block →recent activity