Block #71,094,615

← previous blocknext block →recent activity

Analyzing

Block #71,094,615

15 transactions · 13 stateful · 2026-04-28 14:02:55 UTC

Parallelism

87/100

Blocked

8%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,094,615  ·  15 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

0xb2a1c1b2…e9a0

0x065c9d…c394

4 touches
1 conflict

0xbeedaa50…6fb6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7fa9c0ca…18bc

0x065c9d…c394

4 touches
1 conflict

0x86ebc8bf…0aa1

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xac7bd4c6…a8c5

0x065c9d…c394

4 touches
1 conflict

0x322266fd…529d

0x754704…b603

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

1 conflict on slot 0xb2a1c1b2d1…35e9a0

← previous block·next block →recent activity