← previous blocknext block →recent activity

Analyzing

Block #70,892,507

9 transactions · 8 stateful · 2026-04-27 15:37:00 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,892,507  ·  9 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

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x012e1d85…b80d

0x065c9d…c394

4 touches
1 conflict

0x16135856…1d1e

0x065c9d…c394

4 touches
1 conflict

0x22de5358…cc94

0x065c9d…c394

4 touches
1 conflict

0x625550a4…80a2

0x065c9d…c394

4 touches
1 conflict

0xbb752c7e…6f1e

0x065c9d…c394

4 touches
1 conflict

0xd26bda64…fe73

0x065c9d…c394

4 touches
1 conflict

0x085df2c1…305a

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: 0x34b6552d…112a6f

3 conflicts on slot 0x1b5d2e607a…9999b5

← previous block·next block →recent activity