Block #72,860,084

← previous blocknext block →recent activity

Analyzing

Block #72,860,084

38 transactions · 31 stateful · 2026-05-06 18:13:17 UTC

Parallelism

63/100

Blocked

61%

Avg conflicts / tx

2.11

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #72,860,084  ·  38 txs across 14 waves  ·  depth 14
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

wave w12

wave w13

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

0x60f7fbaf…bd58

0x34b655…2a6f

20 touches
45 conflicts

0x35b85d8e…1edd

0x34b655…2a6f

12 touches
15 conflicts

0x22863bf9…19df

0x34b655…2a6f

10 touches
10 conflicts

0xd0f6f4f2…dffa

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xafd59af5…5257

0xc8689a…ee79

10 touches
10 conflicts

0x71a130e9…9494

0xd32edf…ff58

9 touches
10 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 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: 0x34b6552d…112a6f

45 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity