Block #71,648,075

← previous blocknext block →recent activity

Analyzing

Block #71,648,075

28 transactions · 21 stateful · 2026-05-01 03:32:38 UTC

Parallelism

61/100

Blocked

57%

Avg conflicts / tx

2.11

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #71,648,075  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x79dccb7e…669d

0xd32edf…ff58

21 touches
55 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x928d6b23…5370

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x6af306bb…2e81

0x3bd359…433a

4 touches
1 conflict

0xce8bbe33…b72e

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

55 conflicts on slot 0x79dccb7e43…d9669d

← previous block·next block →recent activity