Block #70,908,877

← previous blocknext block →recent activity

Analyzing

Block #70,908,877

31 transactions · 24 stateful · 2026-04-27 17:26:01 UTC

Parallelism

81/100

Blocked

50%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,908,877  ·  31 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…0002

0xb857c1…9be1

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x2912761f…8d87

0xd32edf…ff58

5 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x09b796cb…a782

0x34b655…2a6f

4 touches
1 conflict

0x1ccbecde…b893

0x34b655…2a6f

4 touches
1 conflict

0x3b3a5945…10d0

0x34b655…2a6f

4 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: 0xb857c13a…1a9be1

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity