← previous blocknext block →recent activity

Analyzing

Block #70,892,468

34 transactions · 29 stateful · 2026-04-27 15:36:44 UTC

Parallelism

76/100

Blocked

48%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #70,892,468  ·  34 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x158399f2…d27b

0xd32edf…ff58

15 touches
28 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x33018431…8f5c

0x188d58…ea8e

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0x33018431…8f5d

0x188d58…ea8e

6 touches
3 conflicts

0xce8bbe33…b72e

0x3bd359…433a

6 touches
3 conflicts

0x7b7bcac3…8fbf

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

28 conflicts on slot 0x158399f2f5…1ed27b

← previous block·next block →recent activity