← previous blocknext block →recent activity

Analyzing

Block #71,094,250

23 transactions · 20 stateful · 2026-04-28 14:00:29 UTC

Parallelism

78/100

Blocked

30%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,094,250  ·  23 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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x131a2e…0da9

8 touches
6 conflicts

0x41755291…977f

0x131a2e…0da9

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x3702b140…97ea

0x34b655…2a6f

4 touches
1 conflict

0x3e1f7818…2fc8

0x34b655…2a6f

4 touches
1 conflict

0x4e01a6b9…ed8e

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: Kuru Exchange: MarginAccount

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity