← previous blocknext block →recent activity

Analyzing

Block #71,700,929

19 transactions · 14 stateful · 2026-05-01 09:24:31 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,700,929  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x1a4ee8d0…6cf3

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0002

0x7e9d3a…9fda

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x7322fb4a…635c

0x1b6862…e19c

6 touches
3 conflicts

0x8d492a5e…69b6

0x065c9d…c394

5 touches
3 conflicts

0x00000000…002c

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

10 conflicts on slot 0x1a4ee8d0de…d86cf3

← previous block·next block →recent activity