← previous blocknext block →recent activity

Analyzing

Block #70,922,426

8 transactions · 7 stateful · 2026-04-27 18:56:15 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,922,426  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x2ce2d49e…d18a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xf8ced9b7…8f62

0x065c9d…c394

3 touches
1 conflict

0xb2225781…b55d

0xd32edf…ff58

3 touches
1 conflict

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x8876d94c…8435

0x2a68ba…90c5

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

1 conflict on slot 0x2ce2d49eac…d8d18a

← previous block·next block →recent activity