Block #71,741,618

← previous blocknext block →recent activity

Analyzing

Block #71,741,618

41 transactions · 26 stateful · 2026-05-01 13:55:31 UTC

Parallelism

81/100

Blocked

65%

Avg conflicts / tx

1.17

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,741,618  ·  41 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x30971fd3…7a9f

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0002

0x7e9d3a…9fda

10 touches
10 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x92219ec9…12e3

0x065c9d…c394

7 touches
6 conflicts

0x0f94ee4c…189c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

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

28 conflicts on slot 0x30971fd371…aa7a9f

← previous block·next block →recent activity