← previous blocknext block →recent activity

Analyzing

Block #70,952,085

12 transactions · 10 stateful · 2026-04-27 22:13:40 UTC

Parallelism

83/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,952,085  ·  12 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x37e1be01…6f19

0x54cd53…9e7d

2 touches
0 conflicts

0xa27fa22d…7dca

0x54cd53…9e7d

2 touches
0 conflicts

0xd1a0adf6…6e55

0x54cd53…9e7d

2 touches
0 conflicts

0x0cc89880…ea71

0x6657d1…8ccc

2 touches
0 conflicts

0x125c33ce…1adb

0x6657d1…8ccc

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity