← previous blocknext block →recent activity

Analyzing

Block #70,877,515

16 transactions · 10 stateful · 2026-04-27 13:57:14 UTC

Parallelism

88/100

Blocked

10%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,877,515  ·  16 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

0x5b2a934f…d088

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x641a369e…b23d

0x065c9d…c394

3 touches
1 conflict

0x6ee466c9…8a65

0x065c9d…c394

3 touches
1 conflict

0x9a6f0c2d…b0bd

0x065c9d…c394

3 touches
1 conflict

0x5e804031…f061

0x73ada1…8be0

2 touches
0 conflicts

0x5e804031…f062

0x73ada1…8be0

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 0x5b2a934f13…c2d088

← previous block·next block →recent activity