Block #71,090,134

← previous blocknext block →recent activity

Analyzing

Block #71,090,134

14 transactions · 11 stateful · 2026-04-28 13:33:05 UTC

Parallelism

79/100

Blocked

18%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,090,134  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x03b4fefa…9a00

0x34b655…2a6f

4 touches
1 conflict

0xcef70a96…db44

0x34b655…2a6f

4 touches
1 conflict

0x18978822…2623

0x34b655…2a6f

2 touches
0 conflicts

0x2905340c…dbc6

0x34b655…2a6f

2 touches
0 conflicts

0x2aab0897…78f7

0x34b655…2a6f

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

2 touches
0 conflicts

0x0fc41e7b…6831

0x98dc6e…8633

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity