← previous blocknext block →recent activity

Analyzing

Block #70,918,195

19 transactions · 16 stateful · 2026-04-27 18:28:08 UTC

Parallelism

79/100

Blocked

25%

Avg conflicts / tx

0.37

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,918,195  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x4eb8e225…6e2a

0xd32edf…ff58

7 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x4cb2b152…2e00

0x131a2e…0da9

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

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

6 conflicts on slot 0x4eb8e22558…6b6e2a

← previous block·next block →recent activity