Block #71,742,339

← previous blocknext block →recent activity

Analyzing

Block #71,742,339

42 transactions · 32 stateful · 2026-05-01 14:00:19 UTC

Parallelism

74/100

Blocked

66%

Avg conflicts / tx

2.05

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #71,742,339  ·  42 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

0x00000000…0002

0x7e9d3a…9fda

22 touches
55 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x3fcb99f6…173f

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb85

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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: 0x7e9d3a8a…4f9fda

55 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity