← previous blocknext block →recent activity

Analyzing

Block #71,090,674

33 transactions · 25 stateful · 2026-04-28 13:36:40 UTC

Parallelism

85/100

Blocked

44%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,090,674  ·  33 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x4ab14837…e1b2

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x131a2e…0da9

6 touches
3 conflicts

0x1c913164…5c2e

0x34b655…2a6f

6 touches
3 conflicts

0x801a6e57…d85c

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe52133fd…b3a7

0x34b655…2a6f

6 touches
3 conflicts

0x47b807a2…3307

0x131a2e…0da9

4 touches
2 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x4ab14837eb…ffe1b2

← previous block·next block →recent activity