Block #71,090,136

← previous blocknext block →recent activity

Analyzing

Block #71,090,136

42 transactions · 33 stateful · 2026-04-28 13:33:06 UTC

Parallelism

69/100

Blocked

58%

Avg conflicts / tx

1.24

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #71,090,136  ·  42 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x801a6e57…d85c

0x34b655…2a6f

8 touches
6 conflicts

0x9d651568…2c87

0x34b655…2a6f

8 touches
6 conflicts

0x1c913164…5c2e

0x34b655…2a6f

8 touches
6 conflicts

0x262a793c…1d06

0x34b655…2a6f

6 touches
3 conflicts

0x3b74ae43…a235

0x34b655…2a6f

6 touches
3 conflicts

0x3c35979a…975d

0x34b655…2a6f

6 touches
3 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: 0x34b6552d…112a6f

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity