← previous blocknext block →recent activity

Analyzing

Block #72,429,131

43 transactions · 23 stateful · 2026-05-04 18:21:17 UTC

Parallelism

58/100

Blocked

78%

Avg conflicts / tx

3.58

Longest chain

18 deep

Execution timeline

did this block parallelize well?

view

block #72,429,131  ·  43 txs across 18 waves  ·  depth 18
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

wave w14

wave w15

wave w16

wave w17

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

0x7867e827…f347

0xd32edf…ff58

35 touches
153 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e70

0x188d58…ea8e

2 touches
0 conflicts

0xfe178917…32ec

0x188d58…ea8e

2 touches
0 conflicts

0xfe178917…32ed

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

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

153 conflicts on slot 0x7867e827e8…15f347

← previous block·next block →recent activity