Block #71,090,119

← previous blocknext block →recent activity

Analyzing

Block #71,090,119

10 transactions · 10 stateful · 2026-04-28 13:32:59 UTC

Parallelism

80/100

Blocked

10%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xa3dc6f35…13e9

0x754704…b603

4 touches
1 conflict

0x8956cb26…42fa

0x73ada1…8be0

4 touches
1 conflict

0x1b4df54f…7afb

0x754704…b603

4 touches
1 conflict

0x2af5f63a…b7b9

0x2e3234…7d90

2 touches
0 conflicts

0x68393815…ea1c

0x2e3234…7d90

2 touches
0 conflicts

0x5e804031…f061

0x73ada1…8be0

2 touches
0 conflicts

0x5e804031…f062

0x73ada1…8be0

2 touches
0 conflicts

0x5e804031…f063

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: 0x754704bc…afb603

1 conflict on slot 0xa3dc6f3549…9513e9

← previous block·next block →recent activity