Block #70,981,915

← previous blocknext block →recent activity

Analyzing

Block #70,981,915

10 transactions · 10 stateful · 2026-04-28 01:32:29 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,981,915  ·  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

0x5d845038…9777

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf6d214b0…8abe

0x34b655…2a6f

4 touches
1 conflict

0x4e638546…0894

0x34b655…2a6f

4 touches
1 conflict

0x3360fb5c…0930

0x34b655…2a6f

2 touches
0 conflicts

0x445b51c5…0be4

0x34b655…2a6f

2 touches
0 conflicts

0x4ec9ff52…e6f7

0x34b655…2a6f

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

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 0x5d845038c6…3b9777

← previous block·next block →recent activity