Block #70,892,148

← previous blocknext block →recent activity

Analyzing

Block #70,892,148

14 transactions · 12 stateful · 2026-04-27 15:34:36 UTC

Parallelism

71/100

Blocked

25%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,892,148  ·  14 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

0x00000000…001c

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

8 touches
6 conflicts

0x09142d14…1dfd

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xad092ae6…b421

0x754704…b603

4 touches
1 conflict

0x591e590f…dac3

0xd18b7e…414b

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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: 0x1b68626d…2de19c

6 conflicts on slot 0x0000000000…00001c

← previous block·next block →recent activity