Block #71,683,607

← previous blocknext block →recent activity

Analyzing

Block #71,683,607

12 transactions · 12 stateful · 2026-05-01 07:29:13 UTC

Parallelism

50/100

Blocked

58%

Avg conflicts / tx

1.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,683,607  ·  12 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

0x935ef60e…f5b9

0xd32edf…ff58

11 touches
15 conflicts

0x51032022…7afa

0x065c9d…c394

5 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x4d42f16e…a6ca

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

15 conflicts on slot 0x935ef60ed7…16f5b9

← previous block·next block →recent activity