Block #70,986,913

← previous blocknext block →recent activity

Analyzing

Block #70,986,913

12 transactions · 11 stateful · 2026-04-28 02:05:45 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,986,913  ·  12 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

0x82754758…a06b

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x35e90c3c…188d

0x065c9d…c394

4 touches
1 conflict

0xf08dab4a…7d77

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa5e87af5…6417

0x065c9d…c394

4 touches
1 conflict

0xa0abc8a3…8380

0x065c9d…c394

2 touches
1 conflict

0xa0abc8a3…8381

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 0x82754758f3…35a06b

← previous block·next block →recent activity