← previous blocknext block →recent activity

Analyzing

Block #70,923,248

20 transactions · 18 stateful · 2026-04-27 19:01:43 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,923,248  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x143dba04…1b98

0x8d66a4…3095

6 touches
3 conflicts

0x1e451306…7993

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1af

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0x462c8be7…4f83

0x8d66a4…3095

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: 0x8d66a43f…113095

3 conflicts on slot 0x143dba04c2…a61b98

← previous block·next block →recent activity