Block #71,090,140

← previous blocknext block →recent activity

Analyzing

Block #71,090,140

12 transactions · 10 stateful · 2026-04-28 13:33:07 UTC

Parallelism

83/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xcef70a96…db44

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x03b4fefa…9a00

0x34b655…2a6f

4 touches
1 conflict

0x00000000…000b

0x24b8be…7f9e

2 touches
0 conflicts

0x80710519…f835

0x2e3234…7d90

2 touches
0 conflicts

0x2905340c…dbc6

0x34b655…2a6f

2 touches
0 conflicts

0x310a7246…2dcb

0x34b655…2a6f

2 touches
0 conflicts

0x0218d038…d5c2

0x73ada1…8be0

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 0xcef70a965c…28db44

← previous block·next block →recent activity