← previous blocknext block →recent activity

Analyzing

Block #70,891,710

41 transactions · 32 stateful · 2026-04-27 15:31:40 UTC

Parallelism

78/100

Blocked

63%

Avg conflicts / tx

1.56

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #70,891,710  ·  41 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x3f4d5641…d2eb

0xd32edf…ff58

17 touches
36 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002c

0x1b6862…e19c

8 touches
6 conflicts

0x37699b20…1073

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 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

36 conflicts on slot 0x3f4d5641a0…8bd2eb

← previous block·next block →recent activity