Block #71,090,521

← previous blocknext block →recent activity

Analyzing

Block #71,090,521

15 transactions · 13 stateful · 2026-04-28 13:35:39 UTC

Parallelism

87/100

Blocked

23%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,090,521  ·  15 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0000

0xc1a578…8e1a

4 touches
1 conflict

0x00000000…0001

0xc1a578…8e1a

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

2 touches
0 conflicts

0x11f25e19…8bb1

0x34b655…2a6f

2 touches
0 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x21d22421…0b7a

0x34b655…2a6f

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity