← previous blocknext block →recent activity

Analyzing

Block #70,846,486

30 transactions · 26 stateful · 2026-04-27 10:30:30 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.93

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,846,486  ·  30 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

0xb2c6dbbe…d7ab

0xd32edf…ff58

13 touches
21 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001b

0x1b6862…e19c

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x3254d19b…f714

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x904fc3c0…00ec

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

21 conflicts on slot 0xb2c6dbbeca…ecd7ab

← previous block·next block →recent activity