← previous blocknext block →recent activity

Analyzing

Block #71,239,618

37 transactions · 25 stateful · 2026-04-29 06:08:07 UTC

Parallelism

73/100

Blocked

56%

Avg conflicts / tx

1.19

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #71,239,618  ·  37 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

16 touches
28 conflicts

0xb1dcb4b3…4b74

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0x2484cc15…5afc

0x34b655…2a6f

10 touches
10 conflicts

0x6f2e60dc…e661

0x34b655…2a6f

10 touches
10 conflicts

0x6f6fc26c…3e34

0x34b655…2a6f

10 touches
10 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

10 touches
10 conflicts

0xafd59af5…5257

0xc8689a…ee79

10 touches
10 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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity