← previous blocknext block →recent activity

Analyzing

Block #71,089,814

13 transactions · 13 stateful · 2026-04-28 13:30:57 UTC

Parallelism

77/100

Blocked

31%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,089,814  ·  13 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

0xa3dc6f35…13e9

0x754704…b603

6 touches
3 conflicts

0x00000000…0001

0x8fd63a…536c

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x8956cb26…42fa

0x73ada1…8be0

4 touches
1 conflict

0xf4e554ca…1a6c

0x73ada1…8be0

4 touches
1 conflict

0x1b4df54f…7afb

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0x8fd63a…536c

4 touches
1 conflict

0x7031bcf6…bfef

0x065c9d…c394

3 touches
1 conflict

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

3 conflicts on slot 0xa3dc6f3549…9513e9

← previous block·next block →recent activity