← previous blocknext block →recent activity

Analyzing

Block #70,917,458

37 transactions · 33 stateful · 2026-04-27 18:23:13 UTC

Parallelism

84/100

Blocked

52%

Avg conflicts / tx

1.03

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,917,458  ·  37 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x517c2718…a42a

0xd32edf…ff58

11 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xb9d2cf20…a668

0x34b655…2a6f

8 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0004

0x63e48b…53f2

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

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: 0xd32edf66…9fff58

15 conflicts on slot 0x517c271862…a1a42a

← previous block·next block →recent activity