Block #70,862,746

← previous blocknext block →recent activity

Analyzing

Block #70,862,746

21 transactions · 17 stateful · 2026-04-27 12:18:50 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,862,746  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x41335ddf…94b9

0x34b655…2a6f

4 touches
1 conflict

0x50822eb0…0b06

0x34b655…2a6f

4 touches
1 conflict

0xd984a5e4…5cfc

0x34b655…2a6f

4 touches
1 conflict

0x2a354a63…0515

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x230c7fc3…9d53

0x34b655…2a6f

4 touches
1 conflict

0x48f53c18…0c05

0xd32edf…ff58

3 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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity