Block #70,995,918

← previous blocknext block →recent activity

Analyzing

Block #70,995,918

9 transactions · 9 stateful · 2026-04-28 03:05:45 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,995,918  ·  9 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

0xefde936f…e602

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb9d2968c…8856

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xaa02277c…538e

0x065c9d…c394

4 touches
1 conflict

0xb5704993…5417

0x065c9d…c394

4 touches
1 conflict

0x57596831…f05b

0x065c9d…c394

2 touches
1 conflict

0x8d16ccb1…996c

0x065c9d…c394

2 touches
1 conflict

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 0xefde936f0f…d1e602

← previous block·next block →recent activity