Block #70,986,596

← previous blocknext block →recent activity

Analyzing

Block #70,986,596

10 transactions · 9 stateful · 2026-04-28 02:03:38 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,986,596  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xac206e47…ef7d

0x34b655…2a6f

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x05c3b7fc…dfbd

0x065c9d…c394

2 touches
0 conflicts

0x1d5a9b48…b9b3

0x065c9d…c394

2 touches
0 conflicts

0x66bb0ace…cba0

0x065c9d…c394

2 touches
0 conflicts

0xdb190209…c042

0x065c9d…c394

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

1 conflict on slot 0xac206e4761…ffef7d

← previous block·next block →recent activity