← previous blocknext block →recent activity

Analyzing

Block #71,742,026

27 transactions · 24 stateful · 2026-05-01 13:58:14 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,742,026  ·  27 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

0xaef5ff54…9b21

0xd32edf…ff58

7 touches
6 conflicts

0x08943ea2…ed03

0x754704…b603

6 touches
3 conflicts

0x846f2172…fd54

0x0555e3…2b9c

6 touches
3 conflicts

0xd77e90ec…8c04

0x3bd359…433a

6 touches
3 conflicts

0xc37ee18a…701b

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x00f7e3b7…e015

0x188d58…ea8e

4 touches
1 conflict

0x00f7e3b7…e016

0x188d58…ea8e

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

6 conflicts on slot 0xaef5ff5445…8e9b21

← previous block·next block →recent activity