Block #71,090,387

← previous blocknext block →recent activity

Analyzing

Block #71,090,387

11 transactions · 8 stateful · 2026-04-28 13:34:45 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,090,387  ·  11 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

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x11f25e19…8bb1

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0x262a793c…1d06

0x34b655…2a6f

4 touches
1 conflict

0x3b74ae43…a235

0x34b655…2a6f

4 touches
1 conflict

0x3c35979a…975d

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: 0xc8689a47…62ee79

1 conflict on slot 0x35b65947f9…9a44d1

← previous block·next block →recent activity