Block #70,892,391

← previous blocknext block →recent activity

Analyzing

Block #70,892,391

14 transactions · 12 stateful · 2026-04-27 15:36:13 UTC

Parallelism

86/100

Blocked

25%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,892,391  ·  14 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

0x7b7bcac3…8fbf

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x5eb9b35d…b6dd

0x065c9d…c394

3 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0x2fb6ddd2…b2a4

0x000000…012a

2 touches
0 conflicts

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

2 touches
0 conflicts

0x2af5f63a…b7b9

0x2e3234…7d90

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

1 conflict on slot 0x7b7bcac3fe…968fbf

← previous block·next block →recent activity