Block #70,998,845

← previous blocknext block →recent activity

Analyzing

Block #70,998,845

12 transactions · 11 stateful · 2026-04-28 03:25:13 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,998,845  ·  12 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

0x2ff6968d…7e43

0x065c9d…c394

4 touches
1 conflict

0x8fb893e6…a352

0x065c9d…c394

4 touches
1 conflict

0x93e15703…9be6

0x065c9d…c394

4 touches
1 conflict

0xac39615b…ffd5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002e

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 0x2ff6968d2c…387e43

← previous block·next block →recent activity