Block #71,090,139

← previous blocknext block →recent activity

Analyzing

Block #71,090,139

15 transactions · 14 stateful · 2026-04-28 13:33:07 UTC

Parallelism

87/100

Blocked

21%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xc108f63d…204f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0xa27fa22d…7dca

0x54cd53…9e7d

2 touches
0 conflicts

0xd1a0adf6…6e55

0x54cd53…9e7d

2 touches
0 conflicts

0x08abfabe…4041

0x6657d1…8ccc

2 touches
0 conflicts

0x2d4a4d95…5115

0x6657d1…8ccc

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