← previous blocknext block →recent activity

Analyzing

Block #73,639,245

21 transactions · 15 stateful · 2026-05-10 08:38:47 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,639,245  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xb46e633d…177f

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xc3cdc1a0…f298

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x93afca4c…b47b

0x1b6862…e19c

4 touches
1 conflict

0x4d3e58e0…a2d7

0x34b655…2a6f

4 touches
1 conflict

0x64461c10…e86d

0x34b655…2a6f

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

6 conflicts on slot 0xb46e633de4…0b177f

← previous block·next block →recent activity