← previous blocknext block →recent activity

Analyzing

Block #72,429,198

35 transactions · 20 stateful · 2026-05-04 18:21:44 UTC

Parallelism

57/100

Blocked

80%

Avg conflicts / tx

3.06

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #72,429,198  ·  35 txs across 15 waves  ·  depth 15
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

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

0x36a2591c…5e4a

0xd32edf…ff58

29 touches
105 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xfa324e43…8897

0x1b6862…e19c

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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

105 conflicts on slot 0x36a2591c6f…a65e4a

← previous block·next block →recent activity