Block #71,090,535

← previous blocknext block →recent activity

Analyzing

Block #71,090,535

20 transactions · 18 stateful · 2026-04-28 13:35:44 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,090,535  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xeebd31ac…0794

0x34b655…2a6f

6 touches
3 conflicts

0x257251ca…49b8

0x34b655…2a6f

4 touches
1 conflict

0x273c679b…c5aa

0x34b655…2a6f

4 touches
1 conflict

0x49f231bb…c1c2

0x34b655…2a6f

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0x63b285f3…87ee

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity