← previous blocknext block →recent activity

Analyzing

Block #71,095,645

25 transactions · 25 stateful · 2026-04-28 14:09:49 UTC

Parallelism

72/100

Blocked

52%

Avg conflicts / tx

1.16

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,095,645  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

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

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity