← previous blocknext block →recent activity

Analyzing

Block #71,746,831

29 transactions · 26 stateful · 2026-05-01 14:30:17 UTC

Parallelism

79/100

Blocked

54%

Avg conflicts / tx

1.03

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,746,831  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x4ec6d392…5eb9

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0002

0x7e9d3a…9fda

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 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

15 conflicts on slot 0x4ec6d39266…995eb9

← previous block·next block →recent activity