Block #71,037,139

← previous blocknext block →recent activity

Analyzing

Block #71,037,139

16 transactions · 15 stateful · 2026-04-28 07:40:05 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,037,139  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x41755291…977f

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xdab207c5…f7e3

0x065c9d…c394

4 touches
1 conflict

0x4cb2b152…2e00

0x131a2e…0da9

4 touches
1 conflict

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0xbdc813a1…7854

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity