← previous blocknext block →recent activity

Analyzing

Block #73,651,918

30 transactions · 23 stateful · 2026-05-10 10:04:03 UTC

Parallelism

67/100

Blocked

61%

Avg conflicts / tx

1.77

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,651,918  ·  30 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

0xcf1dfa55…bfcc

0xd32edf…ff58

19 touches
45 conflicts

0x55bb8e74…fc2f

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xf2438038…5fa7

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

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: 0xd32edf66…9fff58

45 conflicts on slot 0xcf1dfa551f…debfcc

← previous block·next block →recent activity