← previous blocknext block →recent activity

Analyzing

Block #70,909,157

33 transactions · 28 stateful · 2026-04-27 17:27:53 UTC

Parallelism

76/100

Blocked

57%

Avg conflicts / tx

0.91

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #70,909,157  ·  33 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

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0x5a3732cb…edb1

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

8 touches
6 conflicts

0x1c354dc0…96de

0x754704…b603

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

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: 0x754704bc…afb603

15 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity