← previous blocknext block →recent activity

Analyzing

Block #71,450,068

13 transactions · 11 stateful · 2026-04-30 05:30:27 UTC

Parallelism

85/100

Blocked

18%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,450,068  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x86cea35b…bdff

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x463be44a…2830

0x34b655…2a6f

4 touches
1 conflict

0x415574e3…7c1a

0x065c9d…c394

3 touches
1 conflict

0x3968cce9…ea45

0x000000…012a

2 touches
0 conflicts

0x78ae17f2…53be

0x000000…012a

2 touches
0 conflicts

0x00000000…0001

0x010592…1c83

2 touches
0 conflicts

0x00000000…0006

0x010592…1c83

2 touches
0 conflicts

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: 0x34b6552d…112a6f

1 conflict on slot 0x86cea35b12…8ebdff

← previous block·next block →recent activity