← previous blocknext block →recent activity

Analyzing

Block #73,962,740

19 transactions · 16 stateful · 2026-05-11 20:47:14 UTC

Parallelism

63/100

Blocked

44%

Avg conflicts / tx

1.16

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,962,740  ·  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

0x24092f07…3a01

0x3bd359…433a

14 touches
21 conflicts

0xa472d565…9fe4

0x3bd359…433a

14 touches
21 conflicts

0x44ad89ba…cf83

0x8361a5…7777

14 touches
21 conflicts

0xf829b068…36cd

0x8361a5…7777

14 touches
21 conflicts

0x00000000…0000

0x97dc05…7116

14 touches
21 conflicts

0x00000000…0001

0x97dc05…7116

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

2 touches
0 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

21 conflicts on slot 0x24092f0747…513a01

← previous block·next block →recent activity