Block #70,986,514

← previous blocknext block →recent activity

Analyzing

Block #70,986,514

13 transactions · 10 stateful · 2026-04-28 02:03:05 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,986,514  ·  13 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

0xa304a124…cefd

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xde329166…d6be

0x065c9d…c394

3 touches
1 conflict

0x0eef1474…839b

0x065c9d…c394

3 touches
1 conflict

0xcbb00381…b5c5

0x065c9d…c394

3 touches
1 conflict

0xad30ea54…ff9e

0x065c9d…c394

2 touches
1 conflict

0x850433e4…f96d

0x065c9d…c394

2 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: 0x065c9d28…a9c394

1 conflict on slot 0xa304a1247b…64cefd

← previous block·next block →recent activity