← previous blocknext block →recent activity

Analyzing

Block #70,923,197

13 transactions · 11 stateful · 2026-04-27 19:01:22 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,923,197  ·  13 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

0x38ba9ea1…9262

0x065c9d…c394

4 touches
1 conflict

0x6e2b2f4b…558c

0x065c9d…c394

4 touches
1 conflict

0x9cab6d89…f727

0x065c9d…c394

4 touches
1 conflict

0xfede61f0…dbee

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

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 0x38ba9ea176…f39262

← previous block·next block →recent activity