Block #71,092,313

← previous blocknext block →recent activity

Analyzing

Block #71,092,313

22 transactions · 19 stateful · 2026-04-28 13:47:36 UTC

Parallelism

64/100

Blocked

58%

Avg conflicts / tx

1.23

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,092,313  ·  22 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

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xdbc578df…706a

0x34b655…2a6f

10 touches
10 conflicts

0x18d6c74a…0836

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x629de12a…8773

0x34b655…2a6f

6 touches
3 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

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

15 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity