← previous blocknext block →recent activity

Analyzing

Block #71,070,745

28 transactions · 25 stateful · 2026-04-28 11:23:52 UTC

Parallelism

79/100

Blocked

60%

Avg conflicts / tx

1.14

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,070,745  ·  28 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

0x8c49c85c…ee96

0x34b655…2a6f

12 touches
15 conflicts

0x35b65947…44d1

0xc8689a…ee79

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x11f25e19…8bb1

0x34b655…2a6f

8 touches
6 conflicts

0x3e1f7818…2fc8

0x34b655…2a6f

8 touches
6 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x62d6e82b…a750

0x34b655…2a6f

8 touches
6 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 0x8c49c85c3e…afee96

← previous block·next block →recent activity