← previous blocknext block →recent activity

Analyzing

Block #70,908,223

6 transactions · 5 stateful · 2026-04-27 17:21:41 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,908,223  ·  6 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

0x29eeda5f…cd70

0x065c9d…c394

4 touches
1 conflict

0x3cd4bd2b…419d

0x065c9d…c394

4 touches
1 conflict

0x7c2581d9…7a23

0x065c9d…c394

4 touches
1 conflict

0xf2b1892b…d49b

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002d

0x1b6862…e19c

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 0x29eeda5f84…efcd70

← previous block·next block →recent activity