Block #71,070,274

← previous blocknext block →recent activity

Analyzing

Block #71,070,274

15 transactions · 15 stateful · 2026-04-28 11:20:43 UTC

Parallelism

47/100

Blocked

53%

Avg conflicts / tx

1.6

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,070,274  ·  15 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x00027aae…b9c8

0x065c9d…c394

4 touches
1 conflict

0x0108aea0…1419

0x065c9d…c394

4 touches
1 conflict

0x016bd8f2…c85a

0x34b655…2a6f

4 touches
1 conflict

0x03b4fefa…9a00

0x34b655…2a6f

4 touches
1 conflict

0x1630ed91…9774

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 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: 0x34b6552d…112a6f

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity