← previous blocknext block →recent activity

Analyzing

Block #70,892,516

18 transactions · 13 stateful · 2026-04-27 15:37:03 UTC

Parallelism

89/100

Blocked

8%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,892,516  ·  18 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

0x7269e6e3…c2b4

0x065c9d…c394

4 touches
1 conflict

0x807e089e…ca36

0x065c9d…c394

4 touches
1 conflict

0xeba74ac5…cd1d

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x0a892d30…2ba2

0x065c9d…c394

3 touches
1 conflict

0x5d8373b9…233e

0x44b60b…f711

2 touches
0 conflicts

0x5d8373b9…233f

0x44b60b…f711

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 0x7269e6e351…26c2b4

← previous block·next block →recent activity