Block #71,421,574

← previous blocknext block →recent activity

Analyzing

Block #71,421,574

12 transactions · 10 stateful · 2026-04-30 02:20:33 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,421,574  ·  12 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

0xbfca3cd0…5023

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

4 touches
1 conflict

0x6d371116…0523

0xa6afd3…d132

3 touches
1 conflict

0x4d9b110e…959f

0xd32edf…ff58

3 touches
1 conflict

0x00f7e3b7…e017

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

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 0xbfca3cd067…cd5023

← previous block·next block →recent activity