← previous blocknext block →recent activity

Analyzing

Block #71,701,018

13 transactions · 12 stateful · 2026-05-01 09:25:06 UTC

Parallelism

46/100

Blocked

58%

Avg conflicts / tx

1.62

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,701,018  ·  13 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x7f25ab47…fc4e

0xd32edf…ff58

11 touches
15 conflicts

0x18638bfa…e5e8

0x065c9d…c394

7 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x91220b8f…7a05

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 0x7f25ab4726…09fc4e

← previous block·next block →recent activity