← previous blocknext block →recent activity

Analyzing

Block #71,092,138

31 transactions · 26 stateful · 2026-04-28 13:46:26 UTC

Parallelism

68/100

Blocked

62%

Avg conflicts / tx

1.29

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #71,092,138  ·  31 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x214dc988…ba27

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xe6bc2705…d15b

0x34b655…2a6f

8 touches
6 conflicts

0xffedaa84…311b

0x34b655…2a6f

8 touches
6 conflicts

0x8adaa189…de79

0x34b655…2a6f

6 touches
3 conflicts

0x9edc88e6…4a93

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity