Block #71,289,331

← previous blocknext block →recent activity

Analyzing

Block #71,289,331

10 transactions · 8 stateful · 2026-04-29 11:38:57 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,289,331  ·  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

0x8a35acfb…d1ad

0x8d66a4…3095

4 touches
1 conflict

0x468c69b1…af11

0x8d66a4…3095

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0xae503b46…4d67

0x065c9d…c394

2 touches
0 conflicts

0xb3e2c08e…5afb

0x065c9d…c394

2 touches
0 conflicts

0xdf7db195…fbc8

0x065c9d…c394

2 touches
0 conflicts

0xe1f88918…1541

0x065c9d…c394

2 touches
0 conflicts

0xf95adcb4…1844

0x065c9d…c394

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: 0x8d66a43f…113095

1 conflict on slot 0x8a35acfbc1…6bd1ad

← previous block·next block →recent activity