← previous blocknext block →recent activity

Analyzing

Block #70,845,752

11 transactions · 6 stateful · 2026-04-27 10:25:37 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,845,752  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb7bc1a95…446c

0x065c9d…c394

6 touches
3 conflicts

0xc9671b67…d7f7

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb9d0fb60…6c9f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x2fd406b4…07fc

0x065c9d…c394

6 touches
3 conflicts

0x137b6e3d…11f2

0x065c9d…c394

2 touches
1 conflict

0x8956cb26…42fa

0x8c5243…c33e

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

3 conflicts on slot 0xb7bc1a952c…89446c

← previous block·next block →recent activity