← previous blocknext block →recent activity

Analyzing

Block #70,892,510

14 transactions · 14 stateful · 2026-04-27 15:37:01 UTC

Parallelism

79/100

Blocked

21%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x8956cb26…42fa

0x73ada1…8be0

4 touches
1 conflict

0xf4e554ca…1a6c

0x73ada1…8be0

4 touches
1 conflict

0x1b4df54f…7afb

0x754704…b603

4 touches
1 conflict

0xa3dc6f35…13e9

0x754704…b603

4 touches
1 conflict

0x220f4f84…15f8

0x34b655…2a6f

2 touches
0 conflicts

0x313f2565…5b00

0x34b655…2a6f

2 touches
0 conflicts

0x32ee90db…decc

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity