Block #70,998,811

← previous blocknext block →recent activity

Analyzing

Block #70,998,811

7 transactions · 6 stateful · 2026-04-28 03:24:59 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x0515f95c…2d2f

0x065c9d…c394

4 touches
1 conflict

0x2ff6968d…7e43

0x065c9d…c394

4 touches
1 conflict

0x518100e6…64e8

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

0x7cb2f3fa…4836

0x34b655…2a6f

2 touches
0 conflicts

0xac808a27…82db

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 0x0515f95ceb…2d2d2f

← previous block·next block →recent activity