Block #70,922,500

← previous blocknext block →recent activity

Analyzing

Block #70,922,500

12 transactions · 11 stateful · 2026-04-27 18:56: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,922,500  ·  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

0x05a32c54…f922

0x065c9d…c394

4 touches
1 conflict

0xf7f640c9…e345

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xca937d46…17e8

0x065c9d…c394

4 touches
1 conflict

0x36e7a517…12b6

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x0d079864…b74e

0x065c9d…c394

2 touches
1 conflict

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

1 conflict on slot 0x05a32c54dc…adf922

← previous block·next block →recent activity