Block #70,846,115

← previous blocknext block →recent activity

Analyzing

Block #70,846,115

25 transactions · 19 stateful · 2026-04-27 10:28:01 UTC

Parallelism

52/100

Blocked

58%

Avg conflicts / tx

2.64

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #70,846,115  ·  25 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

24 touches
66 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x29514ab2…9696

0x34b655…2a6f

2 touches
0 conflicts

0xb240b520…a88a

0x34b655…2a6f

2 touches
0 conflicts

0xd895ee0b…d301

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

66 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity