Block #71,421,699

← previous blocknext block →recent activity

Analyzing

Block #71,421,699

24 transactions · 20 stateful · 2026-04-30 02:21:24 UTC

Parallelism

67/100

Blocked

60%

Avg conflicts / tx

1.63

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,421,699  ·  24 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

0x7e8dfbf8…e6e2

0xd32edf…ff58

15 touches
28 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xf2d754a2…19d6

0x065c9d…c394

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x78694995…f66e

0x1b6862…e19c

4 touches
1 conflict

0x0dbf9688…c6cf

0xd18b7e…414b

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 0x7e8dfbf83f…ffe6e2

← previous block·next block →recent activity