← previous blocknext block →recent activity

Analyzing

Block #73,979,443

18 transactions · 16 stateful · 2026-05-11 22:39:00 UTC

Parallelism

33/100

Blocked

69%

Avg conflicts / tx

3.67

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,979,443  ·  18 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x536e2740…61ac

0x3bd359…433a

24 touches
66 conflicts

0x00000000…0002

0xa7283d…0ace

24 touches
66 conflicts

0x95fa6aba…eec1

0xa7283d…0ace

24 touches
66 conflicts

0x95fa6aba…eec2

0xa7283d…0ace

24 touches
66 conflicts

0x95fa6aba…eec3

0xa7283d…0ace

24 touches
66 conflicts

0x95fa6aba…eec4

0xa7283d…0ace

24 touches
66 conflicts

0x8fa7a69c…8fd7

0xe26e1a…7777

24 touches
66 conflicts

0xa472d565…9fe4

0x3bd359…433a

24 touches
66 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: 0x3bd359c1…15433a

66 conflicts on slot 0x536e2740da…e461ac

← previous block·next block →recent activity